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

Annotations already flag the surprising profile: destructiveHint=true and readOnlyHint=false on a tool titled 'List'. The description earns credit for explaining that surprise — a list may revoke invalid authority — which is genuine added context. However, it does not say what triggers a refresh versus a revocation, whether the operation requires elevated permissions, or that effects are idempotent (annotations cover the latter).

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 the primary action first and the side effect second, with no filler. It is efficient, though the terse second clause is arguably too compressed to be actionable.

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?

An output schema exists, so return values need not be explained. What is missing is the operational context an agent needs before invoking a destructive list: what causes the revocation, and whether that side effect can be avoided. Adequate but with a clear gap given destructiveHint=true.

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 both required parameters carry descriptions pointing to the source tools (agents_list, inbox_list). The description adds nothing about how agent_id or conversation_id scope the assignee results, so the 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?

States a specific verb and resource: 'Lists tracker assignees'. The resource is distinct from the engineering_* siblings (proposals, approvals, follow-ups), letting an agent distinguish it. It stops short of naming a closest alternative, so it is clear but not fully differentiated.

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 sibling engineering tools or other listing tools such as agents_list. The 'may refresh verification or revoke invalid authority' clause hints at an effect but not at the conditions that should prompt a call.

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