list_tickets

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

No annotations are provided, so the description must carry full behavioral disclosure. It implies read-only via 'Return' but omits pagination behavior, rate limits, authentication needs, and whether results are limited or streamed—important traits for a bulk listing tool.

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 front-loaded with the core purpose, followed by a well-structured bullet list of filters and clear usage guidance. Every sentence earns its place without redundancy.

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 6 optional parameters and 0% schema coverage, the description covers most parameters with valuable enum and format details. However, it misses updated_since and does not address behavioral aspects like pagination or rate limits, leaving some gaps for a bulk tool.

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 description coverage is 0%, so the description must compensate. It provides enum meanings and ISO8601 formats for status, priority, type, created_after, and created_before, but completely omits the updated_since parameter and does not explain filter combination logic.

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 states a specific verb and resource: 'Return all Freshdesk tickets with full fields for reporting and analysis.' It distinguishes itself from siblings by naming search_tickets for company/requester filtering and implying bulk analysis versus single-ticket tools.

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?

It explicitly says when to use it: 'Use this for bulk analysis - e.g. all false positives this month, all high priority open tickets.' It also names an alternative: 'For company or requester filtering use search_tickets instead.'

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