redmine_membership_delete

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

With no annotations, the description carries the full behavioral disclosure burden, but it adds little beyond the schema. The DELETE method and "Requires confirm: true" echo information already present in the schema (the confirm property describes this as a destructive action). It does not disclose irreversibility, permissions needed, side effects, or what happens to related data, leaving significant behavioral ambiguity.

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, efficient sentence with clear front-loading: action first, then endpoint, then the critical requirement. There is no redundant filler, and every element earns its place for a simple delete operation.

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, the description is adequate but not complete. It tells the agent what action to perform and the confirm requirement, but omits context about the destructive nature's permanence, permission prerequisites, and potential impacts on related project memberships. Given no annotations or output schema, a bit more context would make it fully self-sufficient.

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 only 50%, with the id parameter undocumented. The description's endpoint path (/memberships/:id.json) implies id is the membership identifier, which adds a bit of meaning, but it does not explain how to obtain the id, what type of membership it refers to, or any additional semantics. The confirm parameter explanation is redundant with the 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 states a specific verb and resource: "Delete membership", and even gives the exact REST endpoint (DELETE /memberships/:id.json). This clearly distinguishes it from sibling tools like redmine_membership_update and redmine_membership_create, leaving no ambiguity about its 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. The description does not mention that this tool is for removing a user's membership from a project, nor when to prefer it over update/create. The only extra information, "Requires confirm: true", is an invocation requirement, not a usage-selection guideline.

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