fiken_get_contact_person

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

No annotations are provided, so the description bears full responsibility. It only states 'Get', which implies a read operation, but does not explicitly confirm it is read-only, nor disclose any side effects, permissions, or rate limits. This leaves significant ambiguity.

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 of six words, which is concise and front-loaded. However, it may be too terse, lacking any structural hints or additional context that could help the agent without being 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?

Given no output schema, the description should explain what the tool returns (e.g., contact person details). It does not. For a simple GET by ID, the agent is left uncertain about the response. Also, it does not clarify the requirement to provide valid IDs or the relationship between companySlug, contactId, and contactPersonId.

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 coverage is 100% (all parameters have descriptions). The description adds no extra meaning beyond the schema, such as value ranges, format hints, or relationships. Baseline is 3 for high coverage, and no additional value is provided.

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 'Get a specific contact person by ID', specifying the verb (get), resource (contact person), and identification method (by ID). This distinguishes it from sibling tools like fiken_list_contact_persons (list) and fiken_get_contact (different resource).

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 on when to use this tool vs alternatives. It does not mention prerequisites, such as needing to obtain contactId and contactPersonId from list calls, or that it is for retrieving a single contact person versus listing all. No exclusions are provided.

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