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

Annotations already declare readOnlyHint and idempotentHint, and the description adds genuinely useful behavioral context: it 'does not return confirmation secrets' and explicitly includes pending, verified, and unsubscribed owners. This goes beyond the structured annotations without contradicting them.

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 two lean sentences with the action and scope front-loaded. Every clause adds useful information; even the redundant 'Read-only' is short and reinforces the safe, non-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 simple single-parameter list operation, the description covers the status categories returned and a key exclusion (confirmation secrets). It omits response structure and how to source inbox_id, but given the annotations and simplicity, these are minor gaps.

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, inbox_id, has 0% schema description coverage. The description merely implies the target via 'on a Cooper inbox' but does not explain what inbox_id is, where to obtain it, or what format it should take. It fails to compensate for the schema 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 description states a specific verb ('List'), resource ('owner addresses on a Cooper inbox'), and scope ('pending, verified, and unsubscribed'). It distinguishes this from siblings like cooper_list_inboxes and cooper_notify_owner by the resource and outcome.

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?

Usage is implied: call this to inspect owner addresses and their statuses on an inbox. However, there is no explicit when-to-use guidance, no exclusions, and no mention of alternatives such as cooper_add_owner or cooper_notify_owner, leaving the selection largely to inference.

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