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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds non-obvious domain behavior: the ownership constraint on the project, the reviewRequired flag semantics, and the caveat that quantities are not bid-ready — context an agent cannot get from annotations alone.

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 tight sentences with the core purpose front-loaded and no filler. The final caveat sentence is slightly redundant with the preceding reviewRequired sentence but earns its place by clarifying downstream use.

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 enumerated, yet the description usefully names the key fields (quantities, trades, confidence, review status). For a single-parameter read tool this is close to complete; only the provenance of project_id is left 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?

Only one parameter and schema description coverage is 0%, so the schema documents nothing beyond type/pattern/length. The description partially compensates by establishing that project_id must reference an owned project, but adds no format or sourcing guidance beyond that.

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 a precisely scoped resource (an owned project's plan files plus extracted takeoff quantities, trades, confidence, and review status). This is clearly distinguishable from siblings like run_takeoff (which presumably generates a takeoff) and list_projects.

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 usage context ('reviewRequired reports whether any line still needs estimator review') and gives a domain caveat about requiring review before pricing/bidding, but never states when to use this versus run_takeoff or how to obtain a project_id. Usage is implied rather than explicit.

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