get_bedrock_patterns

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the burden. 'Get' clearly implies a read-only operation, and the content scope is specified. However, it does not disclose potential caveats, authentication requirements, rate limits, or output structure. For a simple retrieval tool, this is acceptable but minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, well-structured sentence communicates purpose and scope in 13 words. It is front-loaded with the main action and includes necessary detail without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (no parameters, no output schema), the description adequately conveys what the tool returns: architecture patterns with component relationships and cost considerations. It is sufficient for an agent to know what to expect, though it could offer more detail on how the returned patterns are structured.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has effectively zero user-facing parameters (only the internal Context injection), so the baseline is 4. The description does not need to explain parameters, and the schema already documents the optional context. No additional parameter semantics are required.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Get') and resource ('architecture patterns for Amazon Bedrock applications'), and adds specific scope ('including component relationships and cost considerations'). It distinguishes from sibling tools like analyze_cdk_project and get_pricing by focusing on Bedrock architecture patterns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools or any selection criteria, leaving the agent to infer usage solely from the name and the generic 'Get' phrasing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.