create_contact

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only states 'create a new contact,' implying mutation, but gives no details on side effects, permissions, error states, or uniqueness behavior. This is insufficient for a mutation tool with 14 parameters.

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 two sentences long with no extraneous words. It is front-loaded with the core action. However, it could be slightly more structured (e.g., listing key parameters), but overall it is 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?

Given the tool has 14 optional parameters, no output schema, and no annotations, the description is too minimal. It does not explain return values, error handling, or constraints (e.g., unique name). The agent lacks enough context to use the tool confidently.

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 coverage is 43%, meaning 6 of 14 parameters have descriptions in the schema. The tool description adds only that every field is optional and a name is recommended, but does not explain the meaning of the 8 undocumented parameters (e.g., city, state). It compensates slightly but fails to provide meaningful semantics for most fields.

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 new contact' with a specific verb and resource. It also mentions that all fields are optional but recommends including a name, which distinguishes it from sibling tools like update_contact or search_crm.

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 advises to provide known details and include at least a name, giving basic usage context. However, it lacks explicit when-to-use or when-not-to-use guidance, and does not differentiate from alternatives like update_contact beyond the verb.

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