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

With no annotations, the description carries the full burden. It does disclose one real behavioral trait — the 75% slab-utilization assumption — which materially changes the number, but it omits whether this is a pure calculation with no side effects, where the 'posted rate' comes from, and what the result contains.

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, zero filler, with the core computation front-loaded and the assumption appended where it belongs. Nothing is repeated from the name or title.

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?

No output schema exists, so the description should say more about the returned figure — whether it is a single total, a breakdown of install vs slabs, and what currency. It also leaves the pricing source and any dependency on get_pricing unexplained, which is a gap for a cost-estimation tool.

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%, so sqft, slab_sqft and slab_price_usd are already fully documented with units and defaults; baseline is 3. The description adds the 75% usability heuristic, which is genuinely not in the schema, but no per-parameter meaning beyond it.

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?

Names a specific verb (estimate) and resource (countertop job total cost) and states the formula basis (square feet, install rate plus slabs), which separates it from get_pricing and request_quote. It never explicitly names a sibling, so an agent must infer the boundary rather than read it.

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?

Usage is only implied: call it when you have countertop square footage and want a total-cost estimate. There is no stated when-not (e.g., versus get_pricing for rates alone or request_quote for a formal bid), and the 'posted rate' it depends on is never attributed to a source.

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