docs: Added Amazon Nova provider documentation

[5herlocked]

Overview

Documentation for Amazon Nova Provider

Type of change

Type: New Documentation Page

• Linear issue:
• Slack thread:

Checklist

• I have read the contributing guidelines
• I have tested my changes locally using docs dev
• All code examples have been tested and work correctly
• I have used root relative paths for internal links
• I have updated navigation in src/docs.json if needed

(Internal team members only / optional): Create a preview deployment as necessary using the Create Preview Branch workflow

Additional notes

@ccurme -- thank you so much for your support.

[github-actions]

❌ Import check failed

This PR contains imports from langchain_core that should be imported from langchain instead.

Detailed issues

Analyzing diff for import issues...
 Found 1 import issues:

File: src/oss/python/integrations/chat/amazon_nova.mdx
Line: 200
Issue: Import from langchain.tools instead of langchain_core.tools
Current:   from langchain_core.tools import tool
Suggested: from langchain.tools import tool
--------------------------------------------------------------------------------

 Found 1 import issues that need to be fixed.

Why this is a problem

The langchain package re-exports many modules and classes from langchain_core. When possible, imports should use langchain instead of langchain_core for:

• Better user experience (single import source)
• Consistency across documentation
• Reduced cognitive load for users

How to fix

Replace the imports as suggested above. For example:

• ❌ from langchain_core.messages import HumanMessage
• ✅ from langchain.messages import HumanMessage

🤖 Automated check

This check is based on the latest analysis of langchain re-exports from langchain_core.

[ccurme]

Might be worth adding an entry to this page for discoverability (possibly re-naming it Amazon from AWS, I'm not very clear about the relation between the Amazon Nova and AWS).

Left some questions / nits that can be done in follow-up PRs if desired!

[ccurme]

Suggested change

	| [`ChatAmazonNova`](/oss/integrations/chat/amazon_nova) | ✅ | ❌ | ❌ | ❌ | Model-dependent |
	| [`ChatAmazonNova`](/oss/integrations/chat/amazon_nova) | ✅ | ❌ | ❌ | ❌ | ✅ |

(I think we tend to say it's supported if the chat model supports it generally)

[ccurme]

From what I see in the implementation, strict is propagated as a kwarg, so it ends up in invocation params. Is it true that it validates model support for tool calling? If strict is False and the model does not support tool calling, do we get a different error than we otherwise would?

Typically strict in bind_tools engages schema adherence for tool calls (see docs here).

[ccurme]

structured output may be supported already with the base implementation if you support the tool_choice param, might be worth a try.

[5herlocked]

@ccurme -- Thanks for the inputs. Already working on v1.1.0 of the provider -- structured output mode is definitely on the table, I also need to clean up / modify some of the tool use functionality because it's a little different because of it's dependency on Bedrock.

Will also likely have JS supported in due time.