redmine_user_delete

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

With no annotations, the description carries the burden of behavioral disclosure. It does state the destructive nature of the action and the mandatory confirm: true safeguard. However, it omits details such as irreversibility, cascading effects, and authentication requirements, 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 sentence containing the action, the endpoint, and the key safety requirement. Every component earns its place and no filler is present.

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 description is adequate for a simple tool with only two required parameters: it identifies the resource and the confirmation requirement. However, with no output schema and no annotations, an agent is left to infer response handling and the full implications of a destructive delete operation.

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 endpoint '/users/:id.json' adds meaning to the id parameter that the schema does not provide, and the description reinforces the confirm parameter's meaning. The confirm parameter is already well-described in the schema, so the net contribution is meaningful but not exhaustive.

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 a specific verb and resource ('Delete user') and gives the exact REST endpoint, making the tool's function unambiguous. It clearly distinguishes this from sibling user tools like user_create, user_update, and user_get.

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 gives no guidance on when to choose this tool over alternatives, when not to use it, or what preconditions apply beyond the confirm flag. Some usage context is implied by the name, but no explicit direction is provided.

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