deleteMembership

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

The annotation readOnlyHint: false indicates a mutation, but the description adds nothing about consequences (e.g., permanent deletion, cascading effects, required permissions, reversibility). For a destructive operation, this is a significant gap. The description doesn't contradict the annotation, but it also provides no behavioral detail beyond what the annotation already implies.

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 extremely short ('Delete membership'), which is concise but restsates the tool name with minimal added value. It's under-specification rather than effective conciseness—no front-loading of important constraints or context. Every word is wasted because it adds no new information.

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 mutation tool with one nested parameter, no output schema, and no behavioral annotations beyond readOnly false, this description is grossly incomplete. An agent needs to know the effect of deletion, the meaning of format, and any side effects—all missing. Even minimal context like 'permanently removes membership' or 'requires admin rights' would improve it, but there's nothing.

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 0%, and the description makes no mention of parameters (pathParams, format, membershipId). The agent must rely entirely on the schema, which provides field types and enums but no semantic meaning. The description fails to compensate for the lack of schema descriptions.

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 clear verb ('Delete') and resource ('membership'), which is specific and distinguishes it from other delete tools like deleteIssue or deleteProject. However, it does not elaborate on what the membership refers to or differentiate it from the many sibling delete operations beyond the resource name, so it's clear but not outstanding.

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, prerequisites, or alternatives. The agent gets no help in deciding between this and related tools like deleteMembership vs. other deletes, or whether confirmation or specific conditions apply. There is no mention of usage context at all.

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