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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds meaningful non-annotation context: the returned fields and the corporate-tier-only restriction. It stops short of describing pagination, freshness, or result 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 tight sentences: the first front-loads the action, resource, and returned data, and the second adds the eligibility constraint. Every clause earns its place with no redundancy.

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 zero-parameter read tool with an output schema and strong annotations, the description supplies the purpose, content scope, and tier restriction needed to invoke it correctly. Nothing material is missing from the description.

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 has zero parameters and 100% schema coverage, so there is nothing for the description to clarify beyond what the schema provides. Baseline 4 applies because no parameter-compensation is needed.

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?

"Get the list of team members for the authenticated user's team" is a specific verb+resource, and the description lists the returned dimensions (roles, invite status, join dates). The scoping to the authenticated user's team helps distinguish it from company-level people tools such as get_management_team, though no sibling alternative is named 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?

"Corporate tier only" communicates an eligibility constraint, which is useful usage context. However, it does not explain when to use this tool instead of related people/status tools like get_management_team or get_people_profile, nor does it state exclusions beyond the tier gate.

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