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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds the useful fact that it requires team-admin privileges, but says nothing about result ordering, pagination, or what a report record contains.

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 front-loaded sentence with no filler. However, the brevity comes partly from omitting parameter and paging detail rather than from disciplined phrasing.

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?

No output schema exists, so the description shoulders more burden, yet it omits what a report looks like and how pagination works. For a 5-parameter list tool with zero schema coverage, this leaves an agent guessing about isAll, limit, and offset semantics.

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% across 5 parameters. The description only implies teamId ('a team's') and status ('pending or handled'); it leaves isAll, limit, and offset — including the paging model and the 100 max — completely unexplained in both schema and description.

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?

Specific verb (list) plus resource (a team's wrong-assignment reports) with a clarified scope of 'pending or handled'. It reads distinctly from report_wrong_assignment and update_wrong_assignment_report, though it does not explicitly contrast with has_wrong_assignment_report.

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?

'(team admins)' signals the permission context for use, and 'pending or handled' implies the required status filter, but it never states when to prefer this over has_wrong_assignment_report or how to page through results. Usage is implied rather than guided.

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