get_bedrock_patterns

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

The description aligns with the readOnlyHint annotation, presenting a 'Get' operation. It does not contradict the annotation. However, it adds only content details (component relationships, cost considerations) and does not disclose other behavioral traits like authentication needs or rate limits, but the annotation already indicates a safe read operation.

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?

The description is a single front-loaded sentence with no wasted words. It clearly states what the tool does and includes two key content categories without unnecessary elaboration.

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?

For a simple read-only tool with no parameters and an output schema, the description provides complete context: it identifies the resource, content area, and relevant considerations. The output schema covers return structure, so the description need not detail that.

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 schema shows zero parameters, so there is no parameter information to add. The description mentions the scope ('architecture patterns for Amazon Bedrock applications') which implicitly defines the parameter domain, but with 0 parameters the baseline of 4 applies.

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 states a specific verb and resource: 'Get architecture patterns for Amazon Bedrock applications', and mentions specific contents (component relationships and cost considerations). This clearly distinguishes it from sibling tools like get_pricing or analyze_cdk_project.

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 purpose implies when to use the tool, but the description does not provide explicit guidance or mention alternatives like the pricing or CDK/Terraform analysis tools. No exclusions or when-not-to-use instructions are given.

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