timeiq_person_create

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

The description only states it creates a record and is admin-only. It does not disclose any behavioral traits such as side effects, permissions beyond admin, or whether the record is immediately active. With no annotations, this is insufficient.

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 only one sentence, but it lacks important details for a tool with 7 parameters. It is under-specified rather than concise.

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 7 parameters with no schema coverage, no output schema, and no annotations, the description is grossly incomplete. It does not cover error handling, parameter details, or return values.

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 provides no information about the 7 parameters, including required ones like firstName, lastName, email. With schema coverage at 0%, the description adds no value beyond the schema.

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 the tool creates a new team member record, which distinguishes it from other person-related tools like person_activate or person_update. The verb 'create' and resource 'team member record' are specific.

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 explicitly notes 'Admin only', indicating that only admins should use this tool. It provides clear context for who can use it, but does not mention when not to use it or alternatives for non-admins.

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