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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower; the description adds real value with the 'owned project' access scope and the caveat that quantities require estimator review before pricing or bidding. It stops short of describing pagination or freshness of the extracted data.

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 zero waste; the resource and return contents are front-loaded and the review caveat follows. Every clause earns its place.

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-format detail is unnecessary, and the description still enumerates the key returned fields along with the access scope and data-reliability caveat. Nothing essential for correct invocation is missing.

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?

The schema defines project_id's type, pattern and length but provides 0% description coverage, and the description never explains that parameter. It only implies scope via 'owned construction project,' so it partially compensates without giving format or ownership semantics.

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 (read) and resource (plan files plus extracted takeoff quantities, trades, confidence, review status) with precise scope. It is clearly distinguishable from the write-oriented siblings run_takeoff and export_reviewed_estimate.

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 says to use it 'to summarize quantities or identify pending review,' giving clear triggering contexts. It does not, however, name alternatives such as run_takeoff or export_reviewed_estimate or state when not to use it.

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