zendesk_get_time_tracking

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

With no annotations, the description carries full burden. It discloses the return format but does not explicitly state that the operation is read-only, lacks authentication or rate limit notes, and omits potential side effects. It is minimally adequate but not thorough.

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 two sentences long, front-loading the action and then detailing the return values. Every sentence adds value with no unnecessary words.

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 tool's simplicity (one parameter, no annotations, output schema exists), the description covers the essential purpose and output. It could be improved by adding usage context or behavioral notes, but it is largely complete for basic retrieval.

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 input schema has one parameter (ticket_id) with no description and 0% schema description coverage. The tool description does not elaborate on the parameter beyond the schema, adding no additional semantic meaning. For a simple integer ID, this is acceptable but not helpful.

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 retrieves time tracking data for a specific Zendesk ticket, specifying the output includes total and last update time in seconds and human-readable format. This is a specific verb-resource pair that distinguishes it from sibling tools like zendesk_log_time which logs time.

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 is provided on when to use this tool versus alternatives. There is no mention of contexts where this tool is appropriate or inappropriate, nor any reference to sibling tools like zendesk_log_time for comparison.

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