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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the safety bar is low. The description adds genuinely non-annotated context: a $1.00 USD cost, the multi-source reconciliation behavior, and that continuation/monitoring handoff calls are produced. It stops short of disclosing auth requirements, rate limits, or what a 'source gap' actually means in output.

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?

It is a single front-loaded sentence that leads with the price, which is good practice, but the trailing clause becomes a comma-spliced list of six deliverables that is dense and hard to scan. Efficient in length, weaker in structure.

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?

Because an output schema exists, return values need not be re-explained, and the description does convey what the package contains. However, for a paid, multi-source tool with four fully undocumented parameters and no routing against fifteen siblings, the definition leaves meaningful gaps an agent must guess at.

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 (address, city, unit, state), and the description never references any parameter. It neither explains the required address format nor the role of unit/city/state as disambiguators, so it fails to compensate for the schema 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?

The description names a specific verb and resource ('Create a reconciled multi-source property intelligence package') and enumerates the artifacts it bundles (completeness, source gaps, provenance manifest, continuation calls, monitoring handoff). It is clearly a composite/aggregate tool, which distinguishes it implicitly from the atomic check_* siblings, but it never explicitly contrasts itself with them.

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?

There is no explicit when-to-use, when-not-to-use, or alternative routing. An agent cannot tell from the text whether to call this composite pack or the individual check_property / development_due_diligence tools, nor under what conditions the higher-cost pack is warranted.

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