create_contact_relation

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

With no annotations, the description must disclose behavioral traits. It only says 'Create' without specifying side effects like whether duplicate relations are allowed, if it overwrites existing relations, or required permissions. This is insufficient for a mutation tool.

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 and concise, but it is too brief, omitting important details. It could be expanded with a second sentence without becoming verbose.

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?

Despite having an output schema (not shown), the description does not mention what is returned upon creation (e.g., the relation ID). For a create tool with no annotations, this is inadequate. It lacks context about behavior, return values, and usage.

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?

Description does not explain the parameters. While 'contact_id' and 'related_contact_id' are somewhat self-explanatory, 'relation_type' with a default empty string is not clarified. Given 0% schema coverage, the description should add value but fails to do so.

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 'Create a relationship between two contacts' which clearly identifies the verb (create) and resource (relationship between contacts). It is distinct from sibling tools like 'update_contact_relation' and 'delete_contact_relation', though it could be more specific about what constitutes a relationship.

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 such as updating or deleting relations. There is no mention of prerequisites (e.g., contacts must exist) or when to use this versus other relationship tools.

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