fonzip_forms

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

Annotations already state readOnlyHint=false and openWorldHint=true, and the description adds that one action writes a reply to an answer, which is the main mutation. However, it does not mention consequential side effects encoded in the schema (emails, refunds, membership number assignment, template overwrites), so transparency is only partial.

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 a single front-loaded sentence with no filler; the colon list conveys scope and operations efficiently. It could arguably be more action-oriented, but it earns its place as a concise summary.

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 12-parameter, four-action tool with no output schema, the description is minimal, but the rich input schema supplies required-parameter and action mappings. Missing usage and side-effect context prevents a higher score, yet the schema makes the definition usable.

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 100%, and each parameter already has a description plus square-bracket action tags, so the schema carries the parameter meaning. The tool description adds no parameter detail, which is acceptable under the high-coverage baseline.

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 names the resource ('forms and form answers') and enumerates the four operations (list forms, list answers, answer detail, write a reply), which map directly to the action enum. It is clear enough to distinguish this forms domain from the fonzip_* siblings, though it is a noun-phrase summary rather than a single imperative verb.

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?

There is no guidance on when to use fonzip_forms instead of a sibling such as fonzip_templates or fonzip_donations, and no when/when-not conditions. The action enum and parameter tags imply operation selection, but the description itself gives no usage direction.

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