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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond them: it is free to call ('No charge to read it') and it discloses the shape of what is returned (field states, candidate values with evidence, open questions).

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 first sentence is long, off-topic for a read tool, and front-loads unrelated purpose before the actual behavior. The second sentence is tight and informative, but the preamble costs the definition its front-loaded clarity.

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 an output schema present, return values need not be explained, and the description still summarizes them. For a low-complexity, single-parameter, read-only tool the coverage is nearly sufficient, though it never clarifies where a proposal_id originates or how this differs from read_form/get_form.

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% and the single parameter has no description, so the schema does not carry the load. The description only says lookup is 'by its proposal_id', implying it is the key, but adds no format, source, or retrieval guidance (e.g., where a proposal_id comes from).

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 second sentence states a clear verb+resource with return contents: 'Read a proposal by its proposal_id: every field's state, its candidate values with evidence, and the questions still open.' However, the leading sentence ('Prepare a form from documents: a proposal of every answer...') describes content generation rather than reading, which muddies whether this tool reads or prepares and risks conflation with the sibling prepare_form.

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?

'...before writing' implies this is the read/preview step preceding a write such as commit_proposal, and 'No charge to read it' hints at cost considerations. But it never explicitly says when to use this instead of read_form, get_form, or prepare_form, leaving the routing to inference.

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