post_url_number_address_url_email

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

With no annotations, the description must convey behavioral traits. It lists error codes ('noent', 'exists', 'no_match') which hint at outcomes, but fails to disclose whether the operation is destructive, idempotent, or requires existing resources. Inadequate for a mutation tool.

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 short (two lines) and wastes no words, but it lacks substance. While concise, it sacrifices clarity and completeness.

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 6 parameters and many sibling tools, the description is insufficient. It doesn't explain the tool's role in the broader API, fails to mention return structure (despite output schema existence), and doesn't clarify which type of contact resource is created.

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 83%, so most parameters are described in the schema. The description adds no extra meaning, but the high coverage baseline justifies a 3. No parameter semantics are added beyond the schema.

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', which is too narrow given the tool's name includes 'url', 'number', 'address', 'email'. It doesn't clarify what entity is created, leading to ambiguity. The purpose is vague and doesn't distinguish from sibling tools like 'post_address_number_address_url_email'.

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 usage guidance provided. The description lacks any indication of when to use this tool versus alternatives (e.g., 'post_number_number_address_url_email'). No prerequisites or context are mentioned.

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