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. The description's only added value is telling the agent what the payload contains (members, their role values, and status), which is modest but real context beyond the 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?

A single short noun phrase — front-loaded and free of waste. It is slightly under-specified rather than verbose, but nothing needs trimming.

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-argument, read-only context tool with no output schema, the description covers the broad shape of the return data (members, roles, status) but not the response structure or whether the team is scoped to the current account. Adequate but with clear gaps for an agent that must parse the result.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The role enumeration in parentheses is not a parameter enum here but still usefully signals expected values in the data.

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 the resource domain (team) and enumerates its contents, 'members with roles (owner, admin, member, worker) and status.' It never states the action explicitly (fetch/return), relying on the tool name 'fetchTeamContext' for the verb, so an agent gets the domain but not a clean verb+resource statement.

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?

There is no guidance on when to call this versus the many sibling context tools (fetchTeamChatContext, fetchCustomerContext, fetchProjectsContext, etc.). The agent must infer that 'team' means org members rather than chats or projects from the noun alone.

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