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, covering the safety profile. The description adds useful context that this returns a derived/'advised' roster incorporating capability and measured speed, and that degraded agents are excluded from real-time roles. It does not disclose cost, computation semantics, or whether it triggers any analysis.

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 compact sentence with the read verb front-loaded. It avoids waste, though the parenthetical jargon slightly muddies an otherwise tight statement.

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 0% parameter coverage, the description should explain both the input identifier and the shape of the returned 'advised roster.' It gestures at content (capability + measured speed) but leaves the team_id meaning and the actual return structure unexplained.

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 0% for a single required team_id parameter, so the description carries the full burden and must explain it. It never mentions team_id at all, leaving the agent to guess what identifier it expects (team name vs. UUID vs. roster id). No compensation for the coverage gap.

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 verb ('Get') and resource ('roster') are identifiable, and the parenthetical hints at the computed content (capability + measured speed). However, 'brain-advised' is opaque jargon that an agent cannot reliably interpret, and the description does not clearly distinguish this from siblings like get_team or set_team_roster.

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 explicit statement of when to call this versus get_team, set_team_roster, or other roster-related siblings. The phrase 'degraded agents kept out of real-time roles' faintly implies a use case but names no alternatives and states no prerequisites.

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