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

With no annotations, the description carries the behavioral burden and does disclose some process and deliverables: 30-100 photos, checklist-driven measurements, defect severity, a one-page report, and a signed attestation. It does not state whether the tool mutates data, requires authorization, has cost or duration implications, or how the attestation is handled. The disclosure is useful but incomplete for an unannotated tool.

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?

The description is a single front-loaded sentence with a clear colon-delimited list of report components. It is dense but efficient and avoids repetition. It could be slightly more scannable, but every clause adds a concrete deliverable.

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?

This is a multi-parameter tool with no annotations, no output schema, and zero schema description coverage. The description explains some outputs but leaves critical inputs—address, checklist format, deadline semantics, budget_cap behavior—unexplained. Given the complexity, an agent lacks enough context to invoke it confidently.

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 0% across four parameters, so the description must compensate. It only vaguely gestures at 'checklist' and 'measurements where asked' and never explains address, deadline, or budget_cap. The required address and checklist parameters are especially underspecified given their importance.

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?

The description clearly states what the tool produces: a 'Structured condition report' covering properties, units, vehicles, equipment, job sites, or storm damage. It enumerates concrete report components (photos, checklist, measurements, defect list, report, attestation), making the purpose specific. It does not, however, distinguish itself from siblings like technical_survey or environment_assessment, so it stops short of a 5.

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 implied by the subjects listed—property, unit, vehicle, equipment, job site, storm damage—but there is no explicit guidance on when to choose this over technical_survey, environment_assessment, or other siblings. No exclusions or prerequisites are stated. An agent can infer it is for condition inspections but must guess about alternatives.

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