zendesk_log_time

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

Discloses that time is added to a running total and updates last-update time, and returns amounts in seconds and human-readable format. No annotations were provided, so this is adequate though it could mention if time is additive or replaces.

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 concise sentences, no fluff, front-loaded with action and effect. Every sentence adds value.

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 simple two-parameter tool, the description covers the main action and output. However, it omitted details like ticket existence validation or permission requirements, but given an output schema may provide return info, it's reasonably complete.

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 0%, and the description does not add meaning beyond parameter names. It does not explain constraints (e.g., positive integers) or behavior like error handling, which would compensate for the lack of schema descriptions.

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 verb 'Log time' and the resource 'Zendesk ticket', and distinguishes from siblings like 'zendesk_get_time_tracking' by specifying it adds time rather than retrieving it.

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 explicit guidance on when to use or when not to use, nor alternative tools. Usage is implied for logging time on a ticket, but lacks context like prerequisites or conditions.

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