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

Annotations already declare readOnlyHint=true and destructiveHint=false, so 'Read-only' adds nothing — but the description goes further by disclosing the admin-only authorization requirement and the fact that the response includes pending invites and seat counts, not just active members. That is genuine behavioral context beyond the structured fields. Only gap: no note on response size/pagination for large accounts.

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 core action, followed by a dense but purpose-built enumeration of returned fields, then the scope note and permission gate. The inline parenthetical is long, and 'Read-only' redundantly restates the annotation, but every other clause carries information an agent cannot get elsewhere.

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?

With no parameters and no output schema, the description must carry the entire burden of telling the agent what comes back — and it does, itemizing members, invites, and seat counts. Auth requirements and scope are also covered, leaving no material gap for correct invocation.

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 zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The schema coverage is 100% by definition of being empty.

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?

Opens with a specific verb+resource ('List everyone on the account') and then enumerates exactly what is returned: joined members with name/email/role/join date/default-workspace flag/per-workspace roles, pending invites with sender, timestamp and roles, plus remaining seat count. It also scopes the tool ('Covers the whole account, not just the active workspace'), which no sibling name alone conveys.

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?

States the activation condition clearly (account-wide listing vs. a single workspace) and the permission gate ('Account admins only'). It does not name a sibling alternative (e.g., invite_member as the write counterpart, or list_workspaces for workspace scoping), but for a zero-parameter read tool the implied usage is unambiguous.

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