GenerateBedrockAgentSchema

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

No annotations are provided, so the description carries the full burden. It discloses the tool's progressive approach to handle issues (direct import, simplified version, fallback), which adds useful behavioral context beyond basic functionality. However, it lacks details on error handling, performance, or side effects like file system changes.

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 well-structured and front-loaded with the main purpose, followed by details on the progressive approach and parameter explanations. Every sentence adds value without redundancy, making it efficient and easy to parse.

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 complexity (converting Lambda files with a progressive approach) and no output schema, the description is mostly complete: it explains the purpose, usage, parameters, and return value structure. However, it could benefit from more details on error cases or output specifics to fully compensate for the lack of structured fields.

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?

With 0% schema description coverage, the description compensates by explaining both parameters: 'lambda_code_path' as the path to the Python file containing BedrockAgentResolver app, and 'output_path' as where to save the generated schema. This adds essential meaning beyond the bare schema, though it could specify expected formats or constraints.

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 specific verb 'Generate' and resource 'OpenAPI schema for Bedrock Agent Action Groups', specifying it converts a Lambda file with BedrockAgentResolver. It distinguishes from sibling tools by focusing on schema generation from Lambda files, unlike siblings that handle CDK guidance, nag rules, or construct 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 clear context for when to use this tool: when you have a Lambda file with BedrockAgentResolver and need to generate a Bedrock-compatible OpenAPI schema. It does not explicitly state when not to use it or name alternatives among siblings, but the context is sufficiently clear for its specific purpose.

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