Create a new contact

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

Annotations already indicate this is a write operation (readOnlyHint=false) and non-idempotent. The description adds no additional behavioral context such as required relation existence, uniqueness constraints, or what the API returns upon success. No contradiction exists, but no extra transparency is provided.

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 short and mostly to the point, but the first sentence 'Create a new contact.' duplicates the title and adds no value. The API endpoint line is useful but not essential. It is acceptable but not optimally structured.

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 creation tool with no output schema, the description should at least hint at what the caller can expect (e.g., the created contact's ID or a confirmation). It also does not explain the 'linked to a relation' constraint or the role of the 'administration' parameter. This leaves gaps for a correct invocation.

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 description does not mention any parameters or their meanings. Schema coverage is only 50% for top-level parameters, and while the nested ContactInput has detailed fields, the description fails to compensate for the gap by explaining key inputs like relation_id or the administration selector.

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 new contact person linked to a relation,' which clearly identifies the action and the resource, and distinguishes it from relation-level tools like create_relation. However, the first sentence repeats the title and there is no explicit differentiation from update_contact, so it loses a point.

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, and does not mention any prerequisites (e.g., the relation must exist before linking). It simply restates the function without contextual or exclusionary information.

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