search_additional_addresses

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

The description states a search operation (implying read-only) while annotations set readOnlyHint to false, creating a contradiction. This misleads the agent about the tool's side effects and fails to disclose any behavioral context.

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 extremely brief, bordering on tautology, and does not constitute a meaningful explanation. It lacks structure and substance, providing only a bare phrase that does not help the agent beyond the tool name.

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?

Despite having 5 parameters and no output schema, the description provides no information about request/response behavior, the 'body' array, filtering capabilities, or return format. The tool is severely under-described for an agent to invoke correctly.

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 the schema already documents all parameters. The description adds no additional parameter semantics, but the baseline of 3 applies when the schema carries the full burden.

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 'Search additional addresses' directly restates the tool name, providing no additional specificity. While it identifies a search operation, it fails to distinguish it from sibling tools like list_additional_addresses or get_additional_address beyond the verb itself.

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?

There is no guidance on when to use this tool versus alternatives such as list_additional_addresses or search_contacts. No context about its intended use case or criteria for choosing it is provided.

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