clio_create_contact

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

The description states the tool creates a contact but does not disclose side effects, idempotency, error handling, authentication requirements (beyond mentioning JWT routing), or rate limits. With no annotations present, the description fails to provide sufficient 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 concise with three sentences, front-loading the core purpose. However, it could be restructured to better highlight key usage details, but overall it is efficient.

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 is a create operation with a single opaque parameter and no annotations, the description is incomplete. It omits crucial details about the argument structure, required fields, return output, and behavioral expectations, making it insufficient for an agent to use independently.

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 sole parameter 'arguments' is described as a 'JSON string of arguments for the connector operation,' which adds minimal meaning. The schema coverage is 0%, and the description does not specify the expected structure, required fields, or any constraints, leaving the agent with insufficient information to correctly populate the 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 the tool creates a contact via the Clio connector, distinguishing it from sibling tools like clio_list_contacts or clio_create_bill. However, it does not define what a contact is in Clio context, which could help an agent understand the resource being created.

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 (e.g., clio_list_contacts, clio_get_contact). There is no mention of prerequisites, permissions, or scenarios where creation is appropriate.

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