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 contributes useful content disclosure — that the result bundles roles with status and helper info, paid and pending money, and the team room — but says nothing about visibility/permission scoping or guest access, which the token parameter hints at.

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?

One short sentence with no wasted words, and the returned-content list is front-loaded. The telegraphic noun-phrase construction lacks a leading verb, which costs a bit of immediate readability for an agent scanning tool lists.

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 some burden for describing returns, and it does list the payload contents, which is helpful. However, for a two-parameter read tool in a crowded sibling set, it leaves out when to prefer it over adjacent team/task tools and does not mention the team-id-or-task-id duality that the schema handles.

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%, so both parameters (token with its guest-override explanation, and team_id accepting either a team id or a parent task id) are already fully documented in the schema. The description adds no parameter-level meaning; baseline 3 applies.

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 enumerates what a team request returns (roles with status and helper, money paid and pending, the team room), which implies a read/lookup of a single team, but it never states a verb and reads as a fragment ('A team request: ...'). It does not differentiate from nearby siblings such as team_create or task_tree, so an agent must infer the retrieval semantics from the title and annotations.

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 when-to-use guidance, no exclusions, and no named alternative. Nothing tells the agent whether to call this versus team_create or task_tree when it holds a parent task id rather than a team id.

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