post_address_number_address_url_email

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states 'Creates' without detailing side effects, required permissions, idempotency, or what happens on duplicate or missing required fields. The error codes hint at possible outcomes but are not explained.

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 too brief (two lines) and lacks critical information about how the tool works. It is under-specified rather than concisely effective; every sentence should add value, but here the brevity harms clarity.

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 has 6 parameters (none required in schema, but likely functionally required), many siblings, and an output schema, the description is insufficient. It does not explain how to use the tool, what the output contains, or how to handle required fields despite the schema indicating none.

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 have adequate descriptions in the schema (e.g., type enum, is_default, is_own). The description adds no extra meaning beyond the schema, meeting the baseline expectation.

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 'Creates the ContactNumber' is vague and does not differentiate this tool from siblings like post_number_number_address_url_email or post_email_number_address_url_email. The tool name suggests it creates multiple types (address, number, URL, email) but the description only mentions ContactNumber, causing 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 on when to use this tool versus alternatives. The description only lists error codes (`noent`, `exists`, `no_match`) but does not explain their context or provide any usage recommendations.

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