list_unsubscribe_candidates

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

Annotations indicate read-only and idempotent behavior. The description adds that raw unsubscribe URLs and sender addresses are never returned, which is a behavioral constraint not covered by annotations. It also clarifies the role of 'execute_decisions' in validation.

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 highly concise, with two short paragraphs. The first paragraph states the purpose, and the second adds necessary detail without redundancy. Every sentence adds value.

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?

Given 5 parameters, no output schema, and modest annotations, the description lacks coverage of parameters like sort, limit, offset, and account. It explains the method and key behavioral notes but is not fully complete for an agent to use without additional context.

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?

With 0% schema description coverage, the description must explain parameters. It only explains the 'method' parameter (all, one_click, mailto, manual). Parameters like sort, limit, offset, and account are not described, leaving significant ambiguity.

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 clearly states it lists sender domains with cached unsubscribe methods for one account. It also explains the 'method' parameter values, making the purpose specific. However, it does not explicitly distinguish this tool from siblings like 'execute_decisions'.

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?

The description indicates that validation occurs only during 'execute_decisions', implying this tool is for listing candidates before validation. It provides context on when to use it but lacks explicit alternatives or when-not-to-use guidance.

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