Recommend AI agent configuration

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

The description reinforces annotations (readOnlyHint, idempotentHint, destructiveHint) by explicitly stating 'Deterministic, stateless, read-only — does not store past recommendations.' No contradictions, adds clarity.

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?

Two sentences with front-loaded purpose and concise enumeration of inputs/outputs. No filler or redundant information.

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 complexity (nested objects, many parameters, output schema exists), the description covers purpose, all key input categories, output types, and behavioral traits. Output schema handles return values. Annotations are fully leveraged.

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 description coverage is 33% (only environment subfields mentioned in description). The description adds context about how parameters are used but doesn't list all top-level parameters (task, target_platform). The schema provides descriptions for all parameters, so the description adds marginal value beyond schema.

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 uses a specific verb 'diagnose' and clearly states the resource ('deployed AI agent configuration'). It lists inputs and outputs, distinguishing it from siblings like 'interpret', 'normalize', 'rewrite' which serve different purposes.

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 implies usage for diagnosing agent failures and returns configuration recommendations. While it doesn't explicitly state when not to use it or list alternatives, the purpose is clear and the sibling tools suggest different functionalities.

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