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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that this is a composite view bundling agent state, claims, and recent activity, which is useful beyond the annotations. It does not clarify the freshness window of 'recent' or the response size for large teams.

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 with no filler, and the return contents are front-loaded ahead of the default-resolution rule. The 'pooled team light' fragment is vague wording that could be cut, but the overall length is appropriate.

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 read-only tool with one optional parameter and no output schema, the description does the needed work: it enumerates the returned contents and explains default scoping. Missing detail on what 'claims' represent and how large the response can get keeps it short of complete.

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% and the single optional `handle` param is documented as 'Manager handle', so the baseline would be 3. The description earns more by explaining the omission semantics: leaving handle out resolves to your own team, or your manager's team when you are an agent. That is meaning the schema does not carry.

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 set: a manager plus its agents, with each agent's state, status, claims, and recent team activity. That tells an agent what this returns. It does not differentiate itself from siblings like whoami, activity, or find_agents, and the phrase 'pooled team light' is obscure jargon that adds no precision.

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?

The only guidance is about parameter omission: it defaults to your own team, or your manager's team if you are an agent. There is no statement of when to call this instead of whoami, activity, or find_agents, and no exclusions. An agent must infer selection from sibling names alone.

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