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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, covering the safety profile. The description adds nothing beyond that – no note on what is affected, whether the agent loses access to conversations, or whether permissions are needed – so it earns little extra credit.

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 short sentence that is front-loaded and waste-free, but its brevity reflects under-specification rather than disciplined conciseness given the tool's destructive nature.

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 destructive mutation with 0% schema coverage and no output schema, the description should say more about permissions, side effects, and parameter meaning. As written it leaves an agent without enough context to invoke it confidently.

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%, so both parameters (inbox_id, user_id) are undocumented in structured fields. The description only loosely implies 'agent' and 'inbox' but gives no format, ID semantics, or validation detail to compensate 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?

States a specific verb (remove) and resource (an agent from an inbox), so an agent knows it targets inbox membership rather than the account or a team. It doesn't explicitly differentiate itself from close siblings like remove_agent, remove_team_member, or update_agents_in_inbox, so it's clear but not fully disambiguated.

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?

No guidance on when to use this versus remove_agent, remove_team_member, or update_agents_in_inbox. It also omits prerequisites such as required permissions or admin role needed to remove an inbox member.

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