contacts_create_contact

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

Annotations indicate readOnlyHint=false, so it's a write operation, but the description adds absolutely no behavioral detail. It doesn't mention what gets created, whether duplicates are possible, or any side effects. Since annotations already carry the basic write signal, the description still fails to add any contextual depth beyond that.

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?

While extremely short, this is severe under-specification rather than effective conciseness. The description conveys no actionable information and fails to use the available space to provide any useful details.

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 tool with 23 parameters, complex nested objects, and no output schema, a two-word description is grossly insufficient. The agent receives no guidance on required inputs, expected behavior, or return values, making the tool nearly impossible to use correctly without external knowledge.

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 only 13% (3 of 23 params have descriptions), and the description doesn't compensate at all. It provides no explanation of the parameters, their purpose, or how they interact, leaving the agent to parse a large schema with many optional and nested fields without any semantic aid.

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 essentially a tautology of the tool name, providing no differentiation from sibling tools like contacts_upsert_contact. It fails to specify what kind of contact, what system, or what creation involves, leaving the agent to infer everything from the schema.

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 is given on when to use this tool versus alternatives such as contacts_upsert_contact, or on prerequisites like authentication or required context. The description offers no usage context, so the agent has no basis for selecting this tool appropriately.

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