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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that: it discloses the authentication requirement ('needs an account-wide key') and the plan gating ('Agency / Enterprise'). It stops short of describing return shape or completeness of the matrix.

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?

A single front-loaded sentence that carries the resource, the workflow cue, the plan gate, and the auth requirement with no wasted prose. Docked one point for the stray '[#894f5c]' artifact that has no meaning for an agent.

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 zero-parameter, read-only reference lookup with no output schema, the description supplies what an agent needs to call it: purpose, plan eligibility, and key requirement. The returned matrix contents are only summarized ('roles and the role → capability matrix'), leaving some ambiguity about exact output, but it is adequate.

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 tool takes no parameters, so per the rubric the baseline is 4 with no parameter semantics to document. Schema coverage is trivially 100%.

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 resource (workspace roles and the role → capability matrix) and its end-use (picking a role before assigning a member), which ties it to the assign_workspace_member workflow. It is clearly a read of a role/capability reference, distinct from mutation siblings. Lacks an explicit named sibling comparison, so 4 rather than 5.

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 clear context: use this to obtain the matrix 'so you can pick a role before assigning a member,' which orients the agent to the assign flow. It also gates applicability with 'Agency / Enterprise.' No explicit when-not or named alternatives, so not a 5.

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