post_email_number_address_url_email

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

No annotations provided, so description carries full burden. Only lists error codes (noent, exists, no_match), which hint at existence checks but lack details on idempotency, prerequisites, or success behavior.

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?

Very short (two lines), but under-specified. Error codes listed without explanation. Could be improved by integrating error code context into the description.

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 name's complexity and many siblings, the description is incomplete. It does not explain the tool's scope (e.g., why 'email' in name), parameter relationships, or return value, despite having an 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 description coverage is 83%, so most parameters are described in the schema. The description adds no extra meaning or clarification, especially for the 'number' parameter which lacks schema description.

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 'Creates the ContactNumber', but the tool name includes 'email', 'address', 'url', and 'email', leading to confusion. The resource mentioned does not match the name, making the purpose vague and potentially misleading.

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 siblings like post_address_number_address_url_email or post_number_number_address_url_email. No context or exclusions provided.

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