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

Goes well beyond the annotations by disclosing that the call only 'stages a request' requiring the owner to approve out-of-band with an agent PIN, and warns never to accept the PIN in chat. That approval workflow and security constraint are non-obvious behaviors an agent cannot infer from destructiveHint=true.

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?

Front-loaded with the verb and resource, then the capability glossary, then the approval caveat. The eight-item list is somewhat long and overlaps the schema enum, but each gloss adds value and the ordering keeps the critical caveat visible at the end.

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 no output schema, the description covers everything needed to invoke correctly: the resource domain, the workspace precondition, the blast radius, and the out-of-band approval flow. Nothing an agent needs is missing.

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 real meaning by mapping each enum value to a plain-language gloss (readMail = 'Read my email', sendMail = 'Send email on my behalf'), which the bare enum does not provide, and by clarifying the workspace parameter's ownership requirement.

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 ('Switch ... on or off'), the exact resource (one of eight named capabilities for an access role), and scope (a workspace you own). It enumerates all eight capability values with human-readable glosses, so an agent knows precisely what is being toggled without opening the enum.

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?

Gives a clear precondition ('in a workspace you own') and blast-radius context ('reaches everyone who follows the role at once'). It implicitly separates itself from siblings like set_access_role_mailbox_access and set_access_role_skill_access by scoping to the eight capability names, but never names an alternative or an explicit when-not-to-use condition.

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