create_contact

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

With no annotations, the description carries full burden for behavioral disclosure. It confirms creation but fails to mention side effects, validation rules, default values, permissions, or error behavior. The description is minimal and does not provide meaningful transparency beyond the obvious mutation.

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?

Three sentences, no fluff. The first sentence is slightly redundant with the tool name, but the subsequent sentences are concise and informative. Efficient for a simple create tool.

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?

For a create tool with 6 optional parameters and an output schema (not shown), the description covers key guidance for the two contact types but omits email and phone. It does not explain return value, though output schema may cover that. Overall, adequate but not complete.

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 the description must compensate. It explains contact_type and its effect on required fields (first_name/last_name vs company_name), but ignores email and phone parameters entirely. This partial coverage adds value but leaves gaps.

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 'Create a contact' and differentiates between person and company types. However, it does not distinguish from the sibling tool 'update_contact' nor specify the full scope of what is created (e.g., email, phone fields are missing from the description).

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?

The description provides guidance on which fields to supply based on contact_type ('person' vs 'company'), but lacks explicit context on when to use this tool versus alternatives like update_contact or create_lead. Usage is implied rather than explicitly stated.

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