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

Annotations already cover read-only, non-destructive, open-world safety profile. The description adds useful field-level shape (item states, sources, evidence) but does not state ordering, pagination, or that it requires an existing report. With annotations covering safety, this is adequate but thin.

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 front-loaded sentences, no filler. The field enumeration is long but informative rather than redundant. Could be tightened but nothing 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?

An output schema exists, so return-value explanation is unnecessary; the enumerated fields are a helpful complement. For a simple single-param list tool with annotations, the description is nearly complete, lacking only usage routing and the report_id semantics.

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 coverage is 0% and the single parameter 'report_id' is undocumented. The description says items are listed 'for a report', implying the param identifies the report, but adds no format or constraint detail. With 0 params documented in the schema, the description should compensate more.

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?

Clear verb+resource: 'List the pre-buy diligence checklist items for a report.' It is distinct from get_diligence_checklist and get_diligence_progress, though the description does not explicitly differentiate which sibling to use when. The enumerated fields give a precise sense of what an item is.

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?

No when-to-use, prerequisites, or alternative-tool guidance. With siblings like get_diligence_checklist and get_diligence_progress, an agent gets no signal which to pick. Only implied usage from the name.

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