addressbook_multi_get

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

No annotations are provided, so the description carries the behavioral disclosure burden. It conveys that this is a read-only batch retrieval operation, which is useful, but it does not describe return format, error behavior, or how missing/invalid contact URLs are handled. For a simple fetch tool, this is adequate but not rich.

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 short and front-loaded with the core purpose. The second sentence reinforces usage context, though it slightly repeats the idea of exact URLs. Overall it is well-sized with minimal waste.

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 the tool has no output schema and no annotations, the description could do more to clarify what 'details' are returned and how a successful batch result is structured. It is sufficient for a simple batch fetch with fully documented required parameters, but leaves return-shape expectations to inference.

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 description coverage is 100%, so both parameters are already documented in the schema. The description adds the concept of 'exact' URLs but does not meaningfully expand on the parameter semantics beyond what the input schema provides.

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 a specific action ('batch fetch'), a specific resource ('multiple specific contacts'), and the distinguishing retrieval mechanism ('by their URLs'). This semantically separates it from sibling tools like addressbook_query or list_contacts, which are not exact-URL batch fetches.

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 explicitly gives a usage condition: 'Use when you have exact contact URLs and want to retrieve their details.' It does not mention when not to use the tool or name alternatives, but the stated trigger is clear and actionable.

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