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

Discloses that the tool is read-only, does not contact Agrus or create records, and that output is not binding. Given no annotations, description fully covers behavioral traits.

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?

Three sentences with no waste: first states purpose, second clarifies behavior, third gives usage guidance and alternative. Front-loaded and efficient.

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-only heuristic price tool with no output schema, description explains output nature, behavior, and when to use. No missing context given tool simplicity.

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?

All 4 parameters have schema descriptions (100% coverage), so description adds minimal value beyond field names. The description does not elaborate on parameter usage beyond what schema provides.

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?

Clearly states 'Returns a heuristic ballpark price band for the described AI deployment', specifying verb, resource, and scope. Distinguishes from sibling 'request_proposal' by contrasting non-binding estimate vs tracked request.

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 states when to use: 'when the buyer wants order-of-magnitude pricing before committing to a real proposal' and when not: 'For a tracked, follow-up-able request use request_proposal instead.' Provides clear alternative.

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