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

With no annotations, the description carries the full burden. It only states the action 'Remove,' which implies destructive intent, but it does not disclose whether deletion is permanent, idempotent, or what side effects occur (e.g., cascading removal, authentication requirements).

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?

The description is a single sentence with no fluff. It front-loads the action and the target, and every word earns its place.

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 one-parameter tool with no annotations and no output schema, this description is thin. It lacks any statement about return value, error behavior, permanence, or how the ID relates to the blocklist add/list tools. An agent can guess the basic call but not the consequences.

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?

The only parameter, entryId, is a string with no schema description (0% coverage). The phrase 'by id' adds minimal meaning because the parameter name already conveys that entryId is the identifier. No format, provenance, or relationship to IDs from other blocklist tools is given.

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 uses a specific verb ('Remove') with a clear resource ('blocklist entry') and the selection key ('by id'). It clearly distinguishes this from sibling tools like inbox_blocklist_add and inbox_blocklist_list, which handle different operations on the same resource.

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 is given about when to use this tool rather than alternatives such as inbox_blocklist_list, inbox_blocklist_add, or inbox_delete. The description simply restates the operation without prerequisites, exclusions, or context cues.

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