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

Adds substantial context beyond the readOnly/idempotent/non-destructive annotations: the download is short-lived, exports are scoped to owned estimates, and unreviewed estimates are refused with a specific review_required error carrying a remediation link. This error contract is exactly the behavioral detail an agent needs and cannot get from the schema or annotations.

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 tight sentences that front-load the outcome and precondition before the failure case. 'Never exports unreviewed estimates' largely restates the preceding clause, a minor redundancy, but the definition is far shorter than the amount of useful information it carries.

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?

With an output schema present, return-value shape need not be described, and annotations already cover the safety profile. The description supplies the prerequisites, the error contract, and the artifact lifetime, leaving nothing an agent needs to invoke it correctly.

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 (project_id) with 0% schema description coverage, so the schema documents format constraints but not meaning. The description implies ownership scoping ('an owned Portravo estimate') but never says that project_id identifies the project or how ownership is enforced, so it only partially compensates for the coverage gap.

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 and artifact ('Get a short-lived Excel XLSX download') against a precisely scoped resource ('an owned Portravo estimate after every takeoff line has been reviewed and the estimate is priced or final'). This clearly distinguishes it from siblings like run_takeoff or get_takeoff, which produce or read takeoff data rather than an export.

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?

States the conditions under which the tool succeeds (all takeoff lines reviewed, estimate priced or final) and the failure path (review_required error with a review link). It never names an alternative sibling tool for the not-ready case, but the when/when-not boundary is unambiguous.

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