create_contact

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

The description adds no behavioral context beyond the annotations. Annotations indicate readOnlyHint=false and destructiveHint=false, so the agent knows it's a mutation, but the description doesn't explain side effects, required permissions, or what happens on creation. It doesn't contradict annotations, but it also doesn't add value.

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, but this is under-specification rather than effective conciseness. A single phrase with no expansion or context does not earn its place as a meaningful tool description.

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?

With 28 parameters, no output schema, and minimal annotations, the description is wholly inadequate. It gives no context about what a contact is, the required fields, the expected outcome, or any constraints, making it impossible for an agent to invoke the tool with confidence.

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?

The tool description provides zero parameter semantics. While the schema covers 50% of parameters with useful descriptions (e.g., contact_type_id, name_1), the description itself doesn't compensate for the gaps, especially for required fields like owner_id that lack schema descriptions.

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 'Create contact' is a tautology—it simply restates the tool name without adding any detail about what 'creating a contact' entails. It fails to distinguish this from sibling tools like bulk_create_contacts or update_contact, so the purpose is clear only at the most basic level.

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 no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions, leaving the agent without direction on selecting this over related contact operations.

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