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

With no annotations, the description carries full disclosure duty and succeeds: it reveals that the operation is only staged, not immediately destructive, and that approval happens out-of-band in the owner's browser. The PIN warning is a critical behavioral guardrail that prevents the agent from soliciting credentials in chat. It also flags the default-role restriction, which is non-obvious.

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?

Three dense sentences with no filler: action, prerequisites/exclusion, approval flow, and security rule each earn their place. The most important caveats are front-loaded before the procedural detail.

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 two-parameter tool with no output schema or annotations, the description gives everything needed to execute correctly: target role, prerequisite move, default-role exclusion, owner-approval flow, and the PIN safety rule. If anything, the only implicit piece is that the tool returns a link for the owner, but that is inferable from 'opens the link.'

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 descriptions already cover both parameters comprehensively at 100% coverage, so the description does not need to re-explain them. It adds relevant context — such as the default-role restriction — but does not describe parameter formats. Baseline 3 is appropriate.

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 precise action on a specific resource — delete an access role — and immediately scopes it to roles nobody follows. It is clearly separable from siblings like assign_access_role, create_access_role, and rename_access_role. The staged-request nuance is disclosed without obscuring the intent.

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 explicit prerequisites: members and API keys must be moved to another role first, naming assign_access_role as the tool to do it. It also states an exclusion (the workspace default role cannot be deleted) and explains that the owner must approve the request. This is enough for an agent to know when and how to invoke it responsibly.

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