get_address_number_address_url_email_id

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

No annotations provided. Description only lists error codes, not behavioral traits like side effects, permissions, or rate limits. The agent needs more disclosure.

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?

Two sentences, front-loaded with purpose. Efficient, though could expand on error codes naturally.

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 one of many similar lookups. Description lacks differentiation and context about the returned object, despite presence of 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?

Schema coverage is 0%, and the description does not elaborate on the 'id' parameter beyond implying it identifies a contact number. The description should add details like id format or source.

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 states 'Returns the ContactNumber with the given id', which provides a clear verb and resource. However, the tool name suggests a broader entity (address, number, address, url, email), causing ambiguity. It does not differentiate from siblings like get_email_number_address_url_email_id.

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 versus alternatives. Mentions error codes but no contextual advice.

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