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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds one genuine behavioral fact beyond that: platform staff accounts are included in the result, so the agent should not treat an unexpected entry as an error. It says nothing about ordering, pagination, or result size limits.

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, zero filler, resource and scope front-loaded before the completeness caveat. Nothing could be cut without losing information.

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 output schema, the description carries the return-value burden and does list the returned fields. Minor gaps remain — no ordering, no pagination/limit note, and no statement of whether team_id can be omitted or defaulted — but for a small, bounded list tool this is close to sufficient.

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 coverage is only 50%: the `fields` parameter is documented in the schema, but `team_id` has no description at all. The description partially compensates by making clear that the id targets exactly one team, and it enumerates returned attributes (id, name, email, role, availability), but it never explains the `fields` projection parameter or the availability vs. availability_status naming.

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 (List) and resource (members of one team), and the parenthetical enumerates the returned attributes. It implicitly scopes to a single team, which separates it from list_teams and list_agents, but it never names a sibling or states the boundary explicitly.

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?

Usage is only implied: an agent must infer that this is the read-side counterpart of add_team_member / remove_team_member. The note that every member is returned hints there is no server-side filtering, but no when-to-use or alternative (get_team, get_team_report, list_agents) is offered.

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