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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description does add one useful non-obvious scope rule — platform staff accounts are excluded — but says nothing about pagination, result size, or ordering.

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?

Two sentences, no filler, with the scope and returned fields front-loaded ahead of the conditional usage guidance. Every clause carries information an agent needs.

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 it is appropriate that the description enumerates the returned fields and notes the platform-staff exclusion. It is nearly complete for a simple read tool whose annotations already cover safety, with only pagination/result-size behavior left unstated.

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 the single 'fields' parameter is fully documented in the schema, so the baseline of 3 applies. The description's parenthetical field list (id, name, email, role, availability) loosely overlaps with the enum values but doesn't explain the parameter's filtering semantics beyond it.

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 ('List the agents and administrators of this account') and enumerates the returned fields, which distinguishes it from siblings like list_team_members or list_agent_bots. It also scopes the domain by explicitly excluding platform staff accounts.

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 a concrete precondition: 'Call before inviting, removing or changing the role of a person, or adding someone to an inbox or team,' which maps directly onto siblings such as invite_agent, remove_agent, update_agent_role, and update_agents_in_inbox/team. It stops short of naming those tools explicitly or stating when not to use this one.

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