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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered structurally. The description adds meaningful behavior beyond that: it returns ALL users in the workspace (no filtering argument exists) and specifies the exact fields returned, which matters because there is no output schema. It does not address pagination, result size, or whether inactive users are included.

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, front-loaded with the action and scope, then the return shape, then usage. The final 'useful for' sentence is somewhat generic but does help invocation choice; nothing else is padded.

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 simple zero-parameter read with no output schema, the description covers purpose, return fields, and typical use. The only gaps are pagination/size behavior and whether deactivated users appear — minor for this tool's complexity.

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 (additionalProperties: false), so there is no parameter semantics to add; baseline for a no-parameter tool is 4. The description correctly implies an unfiltered, whole-workspace listing, consistent with the empty schema.

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 opens with a specific verb and resource plus scope ('List users in the workspace') and then enumerates the returned fields (email, display name, ID, role). No user-related sibling exists among the ~100 sibling tools, so there is no ambiguity to disambiguate from, and an agent can tell exactly what this returns.

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 names concrete usage contexts — assigning tasks, looking up team members, referencing users in workflows — which tells an agent when to reach for it. It stops short of exclusions or prerequisites (e.g., whether a scope/permission is required, or when not to use it), so it is clear context without the full when/when-not treatment.

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