team_members

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

No annotations are supplied, so the description carries the burden. 'Detail on' and the returned-field list make it plain this is a read operation and signal what comes back, which is useful behavior disclosure. However, it says nothing about permissions, whether role filtering is exact-match, or how large an 'all' response is — meaningful gaps for an unannotated tool.

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: resource and contents first, then the role-filter purpose with a concrete example, then the decision it supports. Nothing is padded or repeated, and the most actionable guidance is front-loaded.

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 and no annotations, the description does the necessary work of listing the returned attributes and the two filtering modes. It stops short of describing response shape or size when names are omitted, which is the main remaining gap for a two-optional-parameter lookup.

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 100%, so both parameters are already documented, including 'omit for all'. The description adds a real use-case gloss for the role filter ('who is platform?'), but gives no matching rules or format hints beyond the schema. Baseline 3 fits.

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 names a specific resource (team member) and enumerates what is returned (current work, model, roles, presence), plus scope ('one member (or all)'). It doesn't explicitly contrast itself with the roster-oriented siblings like team_status or team_availability, so sibling differentiation is left implicit.

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 clearly states when to reach for the tool: filtering by role to identify who holds a duty ('who is platform?') and picking a person to hand off to or ask for help. The guidance is concrete and example-driven, but it never names an alternative tool or exclusion, so an agent must infer that team_availability or team_status are not the roster lookup.

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