redmine_remove_membership

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

No annotations provided. Description mentions that inherited memberships can't be deleted and that it honors a read-only flag, but lacks details on side effects, error handling, or idempotency. Minimal behavioral context.

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?

Two concise sentences covering purpose and key limitation. No unnecessary words; efficient and front-loaded.

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?

Output schema exists but description doesn't explain return values. For a simple deletion, the description covers essential purpose and a constraint, but lacks details on response behavior or error cases. Adequate but not thorough.

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?

Single parameter 'membership_id' has no description in schema (0% coverage). Description does not elaborate on its meaning, format, or constraints, forcing reliance on the schema alone.

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?

Clearly states action 'remove' and resource 'project membership'. Distinguishes from siblings by specifying inheritance constraint which differentiates from other membership tools.

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 explicit guidance on when to use vs. alternatives. Only mentions a limitation (inherited memberships cannot be deleted) but does not provide context for when to invoke this tool.

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