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

Annotations only supply destructiveHint=true, so the description carries most of the behavioral burden; it adds a 'WRITE' label and the underlying API path, which is useful context. However, it never says whether a duplicate submission creates a second entry, whether the entry can be edited/deleted afterwards, or what permissions are needed — notable gaps for an append operation flagged destructive.

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?

Two short sentences, front-loaded with the WRITE label, then the resource action, the one cross-tool lookup note, and the endpoint. Nothing is padded and no sentence is redundant.

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 9-parameter mutation tool with no output schema, the description covers purpose and employee_id sourcing but omits what the call returns on success and where job_number and time_entry_type_id values come from. Adequate to attempt the call, but not complete enough to call it confidently.

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%, so the baseline is 3, but the description genuinely adds meaning beyond the schema by telling the agent where employee_id comes from (the 'id' returned by kickserv_list_employees) rather than just 'The employee's `id`'. It does not explain time_entry_type_id, the only parameter whose source is ambiguous.

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?

States a specific verb and resource — 'log hours worked by an employee on a job' — clearly a time-entry write, distinguishable from sibling writes like kickserv_add_job_charge or kickserv_add_job_note. The 'WRITE:' prefix and endpoint reference reinforce the purpose, though it never names the read-side counterpart (kickserv_list_job_time_entries) it pairs with.

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?

There is no explicit when-to-use guidance or exclusion versus alternatives such as kickserv_add_job_charge, and no stated prerequisite for the job or employee existing. The only usage-adjacent help is the pointer to kickserv_list_employees for sourcing employee_id, which is a lookup hint rather than a usage rule.

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