get_additional_address

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

With annotations already declaring readOnlyHint, idempotentHint, and non-destructive behavior, the description adds no extra behavioral context. It simply states 'Fetch an additional address', repeating the tool's name without disclosing anything about return values, error handling, or authorization beyond what annotations already imply.

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 a single concise sentence, effectively front-loaded with no fluff. However, it is essentially a tautology of the tool name and title, providing minimal informational value despite its brevity.

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?

For a simple getter with complete schema coverage and reassuring annotations, the description is minimally sufficient. Yet it lacks any mention of the relationship between the additional address and the contact, or what the response should contain, which would be helpful given there is no output schema.

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?

The input schema already describes both required parameters with simple but clear descriptions, giving 100% schema coverage. The description adds no additional meaning to the parameters, so the baseline of 3 applies.

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 uses the specific verb 'Fetch' and the resource 'an additional address', clearly indicating a read operation for a single address. However, it does not explicitly distinguish itself from siblings like list_additional_addresses or search_additional_addresses, though the name and required ID parameters imply a single-record get.

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 provides no guidance on when to use this tool over alternatives. There is no mention that list_additional_addresses or search_additional_addresses should be used for retrieving multiple addresses, nor any context about prerequisites or typical use cases.

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