clokio_add_client_contact

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

Annotations already signal that this is a non-read-only, non-destructive operation, and the description merely restates the mutation without adding behavioral context. It does not disclose duplicate handling, whether the client must exist, response behavior, or side effects, so it adds no transparency beyond the annotations.

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 six words, front-loaded, and contains no filler. Every word contributes to the core action, though its brevity borders on under-specification, which is already penalized in other dimensions.

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 mutation with five parameters, no output schema, and minimal annotation detail, the description is too thin to be fully actionable. It omits required-field context, expected behavior, and any relationship to client or contact lookup tools, leaving the agent to infer too much.

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%, so the description needed to compensate for the five undocumented parameters. 'Add a contact' only loosely maps to the name/role/email/phone properties and 'client' to client_id; it does not explain required fields, formats, or relationships. The added meaning beyond the property names is minimal.

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 states a specific verb and resource: 'Add a contact to a client.' The object of the action and the target are clear, and no sibling tool appears to perform exactly this create operation. It stops short of a 5 because it does not explicitly differentiate itself from related tools like clokio_get_project_contacts or clokio_get_client.

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 offers no guidance about when to use this tool versus alternatives. Sibling tools include read-oriented contact/client lookups, but the description does not mention exclusions, prerequisites, or conditions that would determine when this mutation is appropriate.

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