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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, yet the description adds real value beyond them: role-dependent content (only admins receive pending invitation metadata) and an explicit data-exclusion guarantee ('invitation tokens and delivery payloads are never returned'). These are behavioral traits the annotations cannot express.

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 short sentences, each carrying distinct information (subject, role-gating, data exclusion), with the main action front-loaded. No filler or redundancy.

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 single-parameter read tool with full annotation coverage and no output schema, the description is largely sufficient: it explains what is read, who sees what, and what is withheld. It stops short of noting whether pagination or workspace-membership is required to obtain the roster.

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 for the single workspace_id parameter, but it only alludes to a 'selected workspace' without adding format, sourcing, or constraints. The uuid type and pattern live entirely in the schema, leaving the description adding almost nothing on this dimension.

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 description states a specific verb and resource ('Read the selected workspace roster'), which an agent can contrast with get_workspace_activity or invite_workspace_members without opening a schema. It does not explicitly name sibling tools, but the resource scope is clear enough to route correctly.

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?

Usage is implied by 'read the selected workspace roster' and the mention that only admins see pending invitation metadata, but there is no explicit when-to-use guidance or named alternative for related reads like get_workspace_activity. The agent must infer the selection condition from context.

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