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

Annotations already declare this a safe, read-only, idempotent, non-destructive operation, so the safety profile is covered. The description adds useful substance beyond that by stating it returns a cost range plus contractor guidance, which tells the agent what the call yields.

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 short sentences, zero waste, with the usage trigger front-loaded and the return content following. Nothing to trim.

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?

A read-only calculator with fully documented enum params and no output schema; the description covers the trigger and the return shape, which is what an agent needs. Minor unaddressed gaps are cost assumptions (currency, region), but nothing blocks correct invocation.

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 100% and all three params are enums with documented meanings (job, access, urgency), so the schema carries the parameter burden. The description adds no extra semantics such as currency, region, or how access/urgency shift the result, so the baseline of 3 applies.

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?

States a specific verb+resource: computing plumbing repair/replacement/emergency costs. The domain bound is clear enough to separate it from the electrical/hvac/roofing/solar siblings without opening a schema, though it never names them explicitly.

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?

Gives an explicit trigger ('Use when a user asks what plumbing ... will cost'), which is the right routing condition. No when-not guidance or named alternative is given, but the domain separation is self-evident in a cost-calculator family.

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