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

With no annotations, the description carries the full burden, and it does disclose one genuinely important trait: revocation is permanent for the token. It also signals owner-only authorization implicitly via 'Owner control'. However, it says nothing about what pause/resume do to the node's behavior, whether they are reversible, or any auth/rate mechanics.

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 sentences, front-loaded with the actor and scope, no filler. It is efficient, though the second sentence could be better anchored to the revoke action rather than 'Revocation' in the abstract.

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 zero annotations, no output schema, and 0% schema coverage, the description is under-specified. It omits the distinction between the three actions, the meaning of node_token, and any post-condition, leaving an agent without enough to invoke confidently across all three modes.

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%, so the description must compensate and it largely does not. The enum supplies the action values (pause/resume/revoke) and aligns with the title, but node_token is never explained — no hint about what the token identifies or where it comes from. Only partial compensation for the coverage gap.

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 title states a specific action set (pause, resume, revoke) on a specific resource (contributor node), and the description reinforces the actor ('Owner control'). Combined, an agent can distinguish this from siblings like contributor_register or contributor_checkin. The description alone is a bit thin ('owner control'), leaning on the title for the verb.

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 on when to choose pause vs resume vs revoke, no prerequisites, and no mention of alternatives among the sibling tools. The enum lists the actions but the description never explains which situation calls for which.

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