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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real non-annotation context: the granularity of the returned content and an anti-hallucination directive ('never invent answers') that governs how the agent should treat the field data.

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 content payload is front-loaded and every clause maps to a distinct part of the returned form. The enumeration is dense but each item earns its place; the closing behavioral instruction is short and purposeful.

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 no output schema, the description carries the burden of describing return shape and does so thoroughly, down to PDF field names. It is nearly complete for a single-record read; only the explicit boundary with find_forms/complaint_path is missing.

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?

There is a single required parameter with 100% schema description coverage, and the schema already explains it comes from find_forms or complaint_path. The description adds no further semantics about the id, so the baseline 3 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?

The description concretely enumerates what a single-form retrieval returns: sections, per-field labels/types/required flags/instructions, attachments, submission destination, deadlines, and fillable-PDF field names. The singular 'One form' implies the contrast with a listing tool, but the description body never names find_forms or complaint_path — only the schema does — so sibling differentiation is implicit 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?

'Walk the user through it one field at a time; never invent answers' gives procedural guidance on handling the result, which is useful. However, it never states when to call this instead of find_forms or complaint_path (the id source is only mentioned in the schema), so tool selection is left to inference.

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