create_contact

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

The description states 'Create' which implies mutation, but does not disclose error handling (e.g., duplicate emails), idempotency, permissions, or side effects. Annotations do not provide destructiveHint or idempotentHint, so the description bears the full burden but fails to add 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, which is concise but severely lacking in necessary detail. It achieves conciseness at the cost of completeness.

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 there is no output schema and 5 parameters with 0% schema coverage, the description should provide substantial guidance. It only states the basic purpose, leaving out return value, parameter formats, and behavioral context.

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%, yet the description does not explain any parameter semantics. It does not define the purpose of external_id or how company_id relates to other entities. The required fields are not elaborated.

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 the verb 'Create', the resource 'contact (end-user)', and the platform 'Planhat'. It effectively distinguishes from sibling tools by specifying the resource type, including clarification that it is an end-user contact.

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 like create_user or when not to use it. There's no mention of prerequisites, scenarios, or exclusions.

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