get_number_number_address_url_email_id

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

The description lists error codes but fails to disclose other behavioral traits such as read-only nature, authentication needs, or side effects. Since no annotations are provided, the description should carry this burden but falls short.

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 very short and to the point, but it sacrifices completeness for brevity. It could include more useful information without becoming overly long.

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 large number of similar sibling tools and the existence of an output schema, the description does not provide sufficient context to differentiate this tool or fully understand its behavior. It is incomplete for a get operation.

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 schema has one parameter 'id' with no description, and the tool description does not add any meaning beyond 'given id'. It does not explain what the id represents or its format.

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 the tool returns a 'ContactNumber' given an id, which is specific. However, it does not differentiate from sibling tools like get_address_number_address_url_email_id, which could cause confusion.

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 is provided on when to use this tool versus alternatives. The description does not mention any prerequisites or conditions for use.

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