forms_delete_question

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

No annotations are provided, so the description carries the full burden. It discloses the core behavior (delete) and the index-based addressing, which is essential. However, it does not disclose potential side effects such as irreversibility or the shifting of subsequent question indices, leaving a gap in behavioral transparency.

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 sentence that is front-loaded with the verb 'Delete', directly states the resource and the addressing method, and contains no unnecessary words or repetition.

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 simple two-parameter delete tool with an output schema, the description provides enough information for an agent to invoke it correctly: it identifies the target (form_id) and the 0-based index (item_index). It does not need to explain return values due to the output schema. It could mention index shifting, but that is not required for correct invocation.

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 specifically clarifies that item_index is a 0-based index, which is crucial and not obvious from the schema's bare 'Item Index' title. form_id is self-evident from its name, so no further explanation is needed.

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 clearly states the action (Delete), the target resource (a question from a form), and the addressing method (0-based index). This distinguishes it from sibling tools like forms_add_question, forms_update_question, and forms_move_question.

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 implies usage: use this tool to remove a question from a form. However, it does not explicitly mention when not to use it or point to alternatives. It provides no guidance on preferring this over forms_update_question or forms_move_question for similar operations.

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