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

Annotations already carry the safety profile (destructiveHint=true, readOnlyHint=false), and the description is consistent with them — no contradiction. The description adds modest behavioral context: members can be resolved from multiple sources simultaneously, and the group can be addressed by id, slug, or JID. It does not go further to describe permanence, permission requirements, or behavior on missing members, which is acceptable given the annotation coverage but not additive beyond it.

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 sentences, zero waste. The action is front-loaded, the key scope ('any combination of sources') comes immediately after the verb, and the second sentence covers the addressing flexibility. Every clause earns its place.

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 an 8-parameter destructive tool with no output schema, the description covers the operation, source resolution, and addressing modes while schema and annotations handle parameter semantics and safety. It is adequate but leaves real gaps: no indication of what a successful removal returns, how errors are surfaced, or whether admin permissions are required for the group 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?

Schema description coverage is 100%, so the baseline is 3. The description adds genuine value by clarifying that the source parameters are combinable ('any combination of sources') — a union-then-subtract semantic that is not obvious from reading individual schema entries. This elevates it above the baseline, though the schema already describes each parameter well.

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 ('Remove members from a group') and adds the distinguishing mechanism ('resolved from any combination of sources') with a concrete example. It stops short of a 5 because it does not explicitly differentiate itself from the closely named sibling neuron_remove_member, leaving the 'bulk vs. single' distinction to inference.

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 phrase 'any combination of sources' and the example 'remove everyone on a contact list' imply this is the flexible bulk-removal tool, giving an agent some sense of when to pick it. However, it never names an alternative (e.g., neuron_remove_member for a single member) or states any conditions for when not to use it, so the guidance remains implied rather than explicit.

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