missive_list_contact_booksList contact books (address books). Missive: GET /contact_books.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max contact books to return (default 50, max 200). | |
| offset | No | Number of records to skip (offset pagination). |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description repeats the read-only nature already indicated by annotations (readOnlyHint=true) and adds only the API endpoint. No disclosure of pagination, ordering, or effect on state beyond what annotations provide.
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?
Single sentence with no redundant information. Front-loaded with action and resource. 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?
Tool is simple but description lacks return format details (no output schema) and does not mention defaults or error conditions. Given zero output schema, description should specify that it returns an array of contact book objects.
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 descriptions for both 'limit' and 'offset'. Description does not add any parameter meaning beyond the schema, so baseline 3 is appropriate.
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?
Description clearly states 'List contact books (address books)', specifying the verb and resource. It distinguishes from sibling tools like missive_list_contacts and missive_list_contact_groups by resource name.
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 tool vs alternatives. Does not mention prerequisites, context, or comparison with sibling tools that list contacts or groups.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.