it_ops_analyze_cost

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

Annotations indicate destructive=true, but description doesn't elaborate on side effects or what might be changed; adds auth routing context but no behavioral detail.

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?

Description is brief and structured with args section; no redundancy or excessive length, though it could be more informative.

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?

Tool name suggests cost analysis but no explanation of what it returns, what triggers it, or how it fits with many sibling tools; incomplete for an agent to select and invoke correctly.

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 has no descriptions and coverage is 0%; description only says message is free-text objective and inputs is optional JSON string, which is minimal and doesn't explain content expected.

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 only says 'Run the it_ops domain agent action `analyze_cost`' and explains routing, but doesn't state what analyzing cost actually does or how it differs from sibling tools. The name hints at cost analysis, but purpose remains vague.

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?

No guidance on when to use this tool vs alternatives; mentions JWT/tenant/company scope but no conditions or exclusions.

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