get_scenario_bundle

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

With no annotations, description fully discloses caching mechanism, conditional response, and efficiency gains. No contradictions or hidden behaviors.

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?

Concise three-paragraph structure with front-loaded purpose and efficient use of space—every sentence adds value.

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 read tool with caching, description covers response format and workflow. Could mention error handling or authentication briefly, but sufficient for intended use.

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?

Schema coverage 0%, but description explains cached_hash purpose and behavior. connection_id is not elaborated but is clear from name and required status.

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?

Description states it returns ALL scenario descriptions in a single response, explicitly contrasting with describe_scenario to show its batch nature.

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?

Explicitly tells when to use: replaces 30+ sequential describe_scenario calls, with performance metrics. Also explains caching workflow.

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