delete_question

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

No annotations are provided, so the description must disclose behavioral traits. It states 'Delete' but does not mention that the operation is irreversible, whether it reorders remaining items, or requires specific permissions. For a destructive action, this is a significant gap.

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, very short sentence (6 words). While it is front-loaded, it sacrifices necessary detail for brevity. It does not earn its place because it omits critical information that would require additional sentences.

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?

Given the complexity of a delete operation (irreversible, side effects), the description is incomplete. Although an output schema exists, the description lacks context on error conditions (e.g., invalid index), confirmation, and the relationship to form_id. With 18 sibling tools, the agent needs more to correctly select and invoke this tool.

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?

The input schema has two parameters (form_id and index) with no descriptions. Schema description coverage is 0%. The tool description only says 'Delete the item at the given index,' which hints at index's purpose but does not explain how index is determined or what form_id refers to. The description fails to clarify parameter semantics beyond their names.

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 uses 'Delete the item at the given index,' which specifies a delete operation on an item referenced by index. However, it does not explicitly state that the item is a question within a form, which is important given sibling tools that mention 'question'. The verb is clear, but the resource is ambiguous.

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?

No guidance is provided on when to use this tool versus alternatives like 'move_question' or other mutation tools. The description does not mention prerequisites, such as requiring the form to exist or the index to be valid, nor does it differentiate from similar operations.

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