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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior: it self-checks its arithmetic and that prices are the reader's own figures, not site-derived. It does not address failure modes for unparseable quotes or input limits.

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 the core action front-loaded and the price-provenance caveat second. Slightly loose phrasing ('the reader has, prices and all') costs a little, but there is no filler.

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?

An output schema exists, so return values need not be explained. For a read-only, deterministic conversion tool the description covers the action, the arithmetic check, and the provenance of figures; only error/limit behavior is unstated.

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 is 67%: quote, detail, market and currency carry descriptions, while name and supplier are undocumented in both schema and description. The line about prices being the reader's own figures loosely ties to the currency parameter, but the description otherwise adds no parameter semantics beyond what the 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?

States a specific verb and resource: turning a supplier's or builder's quote into a My Project file/estimate, with an explicit analogy to the site's 'Quote to Estimate'. It is clear what the tool does, though it never names or distinguishes itself from near siblings like check_quote or create_project_file_from_takeoffs.

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 you call it when a reader has a quote in hand, but gives no when-to-use criteria, prerequisites, or explicit routing against alternatives such as check_quote (which presumably validates rather than converts). No exclusions are stated.

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