create_contact

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

No annotations provided, so the description carries full burden. It only says 'Create', implying mutation, but gives no details about side effects, authentication needs, or what happens on success/failure. Insufficient for a writable 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?

Extremely short at one sentence, but this comes at the cost of missing critical information. It is under-specified for a tool with 6 parameters and many siblings, making it unhelpful rather than concise.

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?

Despite having an output schema, the description fails to mention what the output contains or any constraints. For a create tool with many optional fields, it lacks completeness to guide correct invocation.

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 0%, and the description does not explain any parameter meaning beyond their names. All 6 parameters are optional with defaults, but the description offers no context on how to use them or which are important.

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 action 'Create' and the resource 'contact', which is a specific verb+resource. However, it does not differentiate from sibling tools like 'update_contact' or 'list_contacts', but the name itself is distinct enough. Lacks detail on scope or context.

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 vs alternatives, such as 'update_contact' for existing contacts. No prerequisites, error conditions, or recommended scenarios provided.

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