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

Goes well beyond the annotations: it discloses which side effect actually occurs (clearing a passed closing date), the one case that will silently not take effect (max_responses), and the exact billing ($0.001 per call, free on failure). This is the kind of context annotations (idempotent, non-destructive) cannot express.

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?

Three short sentences, front-loaded with the core action, then the edge case, then cost. No filler or repetition of the title.

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 state-change tool with annotations covering safety and no output schema, the description supplies the behavioral nuance that matters: what is cleared, what isn't, and billing. Only a hint about the response/confirmation is absent.

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?

Only one parameter with 100% schema description coverage, which already explains it is a form_id or slug discoverable via forms_list. The description adds nothing about the parameter, 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?

States a specific verb and resource ('Let a closed form take responses again') and implicitly defines itself as the inverse of the sibling forms_close. The max_responses caveat further narrows exactly what state this tool does and does not undo.

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?

Clearly routes the max_responses branch to forms_update ('stays full until you raise it with forms_update'), which is real when-to-use guidance against an alternative. It doesn't mention forms_close or prerequisites like ownership, so it falls short of fully explicit exclusion rules.

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