hires_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 of behavioral disclosure. It only says 'Delete' and 'Use cautiously,' but does not reveal whether deletion is permanent, what happens to questions used in existing job/forms, required permissions, or the response format. The caution is vague.

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 two short sentences, action-first, with a useful caution in the second sentence. There is no wasted wording.

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?

The tool is simple with one parameter, but because it is a mutation with no annotations or output schema, the description should explain consequences for linked entities or whether deletion is reversible. The cautionary note helps a bit but lacks specifics.

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 schema provides 100% coverage for the single 'id' parameter with 'Question ID.' The description adds no meaningful semantic detail beyond calling the resource a reusable question, which is already implicit in the tool name and schema.

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 opens with 'Delete a reusable question from the catalog,' clearly stating the action (delete) and the resource (reusable question). This clearly distinguishes it from other delete_* siblings by specifying the question/catalog context.

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?

It states that the tool deletes reusable questions and adds a caution about using it when deprecating question banks, providing clear usage context. It does not explicitly name alternatives, but for a simple deletion tool the context is sufficient.

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