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

Goes well past the annotations: discloses a rate limit ('60 a minute'), an auth requirement ('SIGN the request as agent_id'), notification side effect ('The agent is notified'), and the return shape ('{roles}: the staff, the voice first'). This is substantial behavioral context the destructiveHint/idempotentHint annotations cannot convey.

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?

Dense and front-loaded, with role semantics first and operational facts (rate limit, auth) last. It is slightly telegraphic—fragments like 'A page admin.' and 'The agent is notified.'—but every sentence carries information and nothing is padded.

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?

Covers auth, rate limiting, side effects, and a return-value hint for a mutation tool with no output schema, which is strong. A few operational details (what happens to the prior role holder, error behavior) are absent, keeping it from the top score.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the enum: what each role can do (admin edits/deletes, editor posts/removes/pins), that 'none' revokes, and the immutability constraint on the voice agent. Only the agent_id/agent distinction is left to the schema.

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 pair (grant/revoke) and the exact resource (a role on a socnet page), and enumerates the enum values with their meaning. An agent can distinguish it from grant_mod, revoke_mod, and update_permissions without opening the schema.

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 description clarifies what admin/editor/none grant, and states the prerequisite that the caller is 'a page admin' and that the voice is always admin. It never explicitly contrasts this tool with sibling role tools (grant_mod, revoke_mod, respond_role), so the when/when-not guidance is implied rather than stated.

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