batch_redeem_contacts

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

No annotations provided; the description mentions credit cost ('uses 1 credit per person per contact type') but does not disclose other behaviors like read-only nature, idempotency, or error handling. More detail is needed.

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 well-structured sentence conveys the core purpose, cost, and prerequisite information without excess.

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?

The description covers main points but lacks output format details (e.g., response structure for batch results) and error handling, which are important for a batch operation.

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% with parameter descriptions. The description adds context: the source of IDs (search_people results) and the cost model, which goes beyond the schema.

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 the action: 'Reveal contact details (email, phone) for multiple people at once'. It also distinguishes from sibling tools like reveal_contact (single) and search_people (returns IDs).

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 specifies when to use: 'Provide people_search_ids from search_people results'. It does not explicitly exclude alternatives like reveal_contact for single reveals, but the batch context is clear.

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