create_contact

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

With no annotations, the description must bear the full burden of behavioral disclosure. It states 'Create a new contact,' implying a write operation, but fails to specify any side effects, required permissions, idempotency, or what happens on success (e.g., returns the created contact). The word 'owner' adds minimal behavioral context.

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 a single sentence, but it lacks essential details, making it under-specified rather than concise. It could be expanded to include parameter structure or usage notes.

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 that there is an output schema (though not visible here), the description should at least hint at what is returned. It does not cover error scenarios or the format of the JSON string. For the complexity of the parameter, the description is incomplete.

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 schema has 0% description coverage, meaning the parameter 'contact_json' has no documentation. The description says 'contact_json is a JSON object string,' but does not specify the expected structure, required fields, or example format. This is a critical gap for a complex string parameter.

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 (owner).' This specifies the action (create) and the resource (contact), and adds context about it being an owner. The name 'create_contact' itself clarifies the purpose, though it does not distinguish from sibling tools beyond the resource type.

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 provided on when to use this tool versus alternatives like create_animal or create_appointment. There is no mention of prerequisites, such as requiring an existing user or authentication, nor any exclusions.

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