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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, but the description adds substantial operational context: what is returned, what API access means, who sees key counts and AI app connections, and the brand-limited visibility rule. This goes well beyond the structured safety hints.

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?

The description is front-loaded with the purpose and returned data, then moves to auth requirements. Every sentence carries distinct information: return contents, API access meaning, permission scoping, and OAuth conditions, with no redundant filler.

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?

There is no output schema, so the description correctly explains the return shape (members, invites, seats, per-member details). Combined with annotations covering safety and idempotency, and the description covering auth and visibility rules, an agent has everything needed to call the tool correctly.

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% and there is only one parameter (workspace_id), which the schema already describes as coming from whoami. The description adds no additional parameter syntax or formatting detail, so the 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?

The description states a specific verb and resource: 'List the people in a workspace', then enumerates the exact members and invites returned. It distinguishes itself from the sibling manage_workspace_member by being purely a read operation with no mutation language.

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?

It gives clear auth and context prerequisites: 'Works with an API key that has the Manage team permission' or OAuth when the user is an owner or admin. It does not explicitly name when to choose this over alternatives, but the read-only framing and sibling names make the use case implicit.

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