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

Annotations already declare it is a non-readonly, non-idempotent, non-destructive mutation, and the description adds genuinely new behavior: no values are set at this stage, the output carries a 'udid' field, and the draft lands in the agent's write scope (SSR cascade). It stops short of saying whether repeated calls create duplicate drafts or what happens to abandoned drafts.

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 critical constraints (draft only, no values yet, udid in result) are front-loaded and easy to scan. The trailing '| EN: form answer, submission, response, prepare, submit' keyword block adds little operational value and dilutes an otherwise tight description.

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 creation tool with no output schema, the description covers input provenance, the exact return field name, downstream consumers, and the scope implication. An agent can chain it correctly without opening anything else.

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 100%, so the baseline is 3; the description adds value by telling the agent where to obtain the form_udid (from list_formdefs) rather than leaving it to guess the source. No format details beyond the schema's 32-hex note, which is appropriate.

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?

States a specific verb and resource (create a form-answer draft, status 'draft') and immediately distinguishes it from the siblings that finalize or read it (submit_form_answer, show_form_answer). The parenthetical that the draft is empty removes any ambiguity about what 'prepare' means here.

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?

Gives an explicit pipeline: get form_udid from list_formdefs, call this, then set values with submit_form_answer and use the returned udid for submit_form_answer/show_form_answer. The alternative/next-step tools are named along with the condition that selects them.

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