create_contact

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

Annotations indicate destructiveHint=true, which matches the creation action. Description adds behavioral context: first_name is required, and phone and country_code enable messaging. No contradictions with annotations.

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?

Two sentences, no redundant information. Every sentence adds value: first sentence states purpose, second provides usage guidance on required and optional fields. Highly 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?

No output schema, but tool is simple. Description covers creation, required field, and optional fields for messaging. Lacks details on return values or error handling, but adequate for a basic creation tool given annotations and 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 0%, so description must compensate. It explains first_name (required) and that phone+country_code are needed for messaging, but does not describe email or last_name. Some value added but not for all parameters.

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?

Description clearly states 'Crea un nuevo contacto en Wasapi' (creates a new contact in Wasapi), with specific verb and resource. It includes required field and optional fields for messaging, distinguishing it from sibling tools like update_contact or delete_contact.

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?

Description implies when to use (to create a contact) and suggests including phone and country_code to send messages, but lacks explicit when-not-to-use or comparisons to alternatives. It provides minimal guidance on context beyond creation.

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