fiken_create_contact_person

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

Annotations indicate readOnlyHint=false, and the description aligns with a write operation. However, beyond that, no behavioral traits are disclosed (e.g., idempotency, error behavior, auth requirements). The description adds minimal transparency beyond 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 very short (one sentence), which is concise but at the expense of necessary detail. It lacks front-loaded parameter information, making it insufficient for tool invocation.

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 complexity (5 parameters, nested object, no output schema) and low schema coverage, the description is completely inadequate. It fails to provide essential context for a create operation, such as required fields or response format.

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% (only country has a description). The description does not explain any parameters, leaving the agent without guidance on how to use the 5 parameters, especially the nested address object.

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 'Adds a contact person to a contact' clearly states the action (adds) and the resource (contact person). It distinguishes from sibling tools like list, get, update, delete contact persons. However, it could be more explicit that this creates a new contact person under an existing 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?

No usage guidelines provided. The description does not specify when to use this tool versus alternatives (e.g., update or list), nor does it mention prerequisites like having an existing contactId.

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