zendesk_get_ticket_audits

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

With no annotations, the description carries the burden of disclosure. It specifies that each audit entry records what changed, who made the change, and when, giving a good sense of the read-only nature and output structure. It does not mention limits or edge cases, but the coverage is sufficient for a simple read operation.

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 with no extraneous information, front-loading the primary action and purpose. Every sentence adds value, making it efficient and easy to parse.

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 simplicity of the tool (one required parameter, no output schema), the description adequately explains the return content (change entries with who and when). It does not detail pagination or ordering, but the use case for tracing history is well addressed.

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 schema covers the single parameter ticket_id with description 'The ID of the ticket' (100% coverage). The description does not add further context about the parameter format or constraints beyond what the schema provides, meeting the baseline for high coverage.

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 the full field-level change history for a ticket, using a specific verb and resource. It distinguishes itself from sibling tools like zendesk_get_ticket (current state) and zendesk_get_ticket_metrics (metrics) by focusing on historical changes.

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 provides clear context by stating the tool is 'useful for tracing how a ticket evolved over its lifetime.' However, it does not explicitly exclude alternative tools or provide when-not-to-use guidance, though the use case is well implied.

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