delete_question

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

The description labels the action as 'Remove' (destructive) but provides no annotations and fails to disclose behavioral traits such as whether associated options are also deleted, if the operation is reversible, or any authorization requirements.

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 concise (single sentence, 6 words) but omits critical details like required parameters and behavioral context. It could be expanded without losing conciseness.

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 no parameters, no output schema, and no annotations, the description is woefully incomplete. For a deletion tool, it should indicate how to specify the target question and what happens to dependent data.

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?

Although the schema has 0 defined parameters (100% coverage), the description does not clarify what input is required (e.g., question ID). With additionalProperties: true, the agent is left to guess the expected fields.

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 'Remove a question from the questionary' clearly states the verb (Remove) and resource (question), distinguishing it from sibling tools like delete_question_option. It is specific enough to convey the core function.

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 update_question or delete_question_option. No prerequisites, examples, or exclusions are mentioned.

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