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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description goes well beyond them: it discloses the permission model, the exact returned field set and role vocabulary, and the 'owner first' ordering. That ordering and cardinality behavior is not derivable from the schema or annotations.

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 tight sentences, front-loaded with the definition, then the disambiguation, then the follow-up routing. No filler, and nothing is repeated from the schema or annotations.

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 a single required parameter, no output schema, and annotations covering the safety profile, the description fills the remaining gaps by documenting the return shape and ordering in prose. Nothing an agent needs to select or call this correctly is missing.

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?

There is only one parameter and schema coverage is 100% (workspace_id is described with its provenance in list_workspaces), so the schema does the work and the 3 baseline applies. The description clarifies the returned user_id but adds nothing about workspace_id semantics or format.

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 verb and resource ('Lists the team members of a workspace') and immediately qualifies the scope: login members, not tagged people. It enumerates the returned fields (user_id, email, name, role) and explicitly names the sibling it is not (list_workspace_people), so an agent can distinguish it without opening any schema.

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 the eligibility condition ('Any member can call it'), an explicit exclusion versus list_workspace_people, and names the downstream tools the returned user_id feeds into (update_workspace_member_role, remove_workspace_member). The when-to-use and when-not-to-use cases are both covered.

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