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

Annotations declare this is a write (readOnlyHint=false) that is non-destructive, and the description's 'Removes a member from your promoting list' is consistent. It adds genuinely useful context beyond annotations by disclosing the JWT auth requirement and clarifying the scope of the removal (promotion list only, not the member). It omits whether the action is reversible or what happens if the member isn't listed.

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 short, front-loaded sentences with no filler. The auth prerequisite is stated first, followed immediately by the effect. Efficient, though minimal.

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 one-parameter mutation tool with annotations covering the safety profile and no output schema, the description covers the core behavior and auth requirement. It is adequate but thin: it never addresses the handle value, list-membership expectations, or failure behavior.

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 single required 'handle' parameter has 0% schema description coverage, so the description carries the burden of explaining it and does not mention it at all. The parameter is arguably self-evident from its name, but the definition leaves all syntax/format meaning to inference.

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?

States a specific verb and resource: removing a member from the 'promoting list'. Combined with the name network_unpick and the sibling network_pick, the inverse operation is unambiguous. It does not explicitly name network_pick as its counterpart, but the intent is clear.

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 only guidance is the prerequisite 'Requires a JWT'. There is no statement of when to use this versus network_pick or network_my_picks, nor any condition or exclusion. Usage must be inferred entirely from the name.

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