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

With no annotations, the description carries the full behavioral burden. It does disclose an important trait: the categories are unscreened and no determinations are established, which prevents an agent from treating output as findings. It omits return shape, size, and whether any auth or entitlement applies.

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, front-loaded with what the tool returns, then the caveats. The second sentence is a dense four-item negation list but every item carries distinct meaning, so little is wasted.

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?

For a zero-param read tool with no output schema and no annotations, the description covers purpose and caveats but says nothing about what a checklist entry actually contains or how the catalog feeds the downstream defect-suggestion tool. That relationship is the main missing piece.

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 tool takes zero parameters, so the schema has nothing to explain and there is no semantic gap for the description to fill. Baseline 4 applies.

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?

Specific verb plus resource ('Retrieve generic property-condition evidence checklists'), and the word 'generic' plus 'Categories have not been screened for any property' implicitly separates it from the property-specific sibling suggest_property_condition_defects. It never names that sibling outright, so differentiation is inferential rather than explicit.

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 disclaimer list ('No repair-cost, legal entitlement, market-value adjustment or tax deduction is established') implies this is a preparatory catalog lookup rather than an analysis tool, but the description never states when to reach for it or what to do next. Usage has to be reconstructed from the negative framing.

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