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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint. The description adds useful behavioral details: reading is free ('No charge to read it') and the response contains field states, candidate values with evidence, and open questions. However, the off-topic first sentence adds noise and undermines the overall behavioral contract.

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 description is not concise: the first sentence is entirely extraneous and misdirects the agent. The relevant content appears in the second and third sentences, violating the front-loading principle. A short, focused description would be much more effective.

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 one-parameter read operation with an output schema and supportive annotations, the core information is present: what the proposal contains and that reading is free. However, the contradictory opening sentence and lack of any differentiation from sibling tools leave the definition incomplete and potentially misleading.

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%, so the description must compensate. It explicitly says 'Read a proposal by its proposal_id', clarifying that the sole parameter is the identifier used to fetch the proposal. This is sufficient for a single string parameter.

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 title and second sentence state a clear read operation ('Read a proposal'), but the first sentence describes a completely different workflow ('Prepare a form from documents'), likely copy-pasted from another tool. This conflicts with the tool's actual purpose and forces an agent to disambiguate contradictory instructions.

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 description gives no guidance on when to use get_proposal versus alternative tools like get_form, read_form, or prepare_form Ś the wrong first sentence even suggests this tool is for preparing forms. No when-to-use or when-not-to-use conditions are provided.

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