filter_tickets

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It discloses critical constraints: the query must be wrapped in double quotes and per_page has a max of 100. It also explains pagination via page and per_page. It does not mention authentication or side effects, but as a filter/read operation, immutability is implied.

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 well-structured: a one-sentence purpose, a critical syntax note with five illustrative examples, and a clear Args list. Every sentence contributes useful information without unnecessary fluff.

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?

With an output schema present, return-value details are not needed. The description covers the query language syntax, quoting requirement, pagination, and parameter constraints, making it complete for correct invocation. It also provides practical examples for typical use cases.

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 provides no property descriptions (0% coverage), but the description explains each parameter thoroughly: query with the double-quote requirement, page as a page number, and per_page with a max of 100. This adds substantial meaning beyond the raw schema types and defaults.

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 specifies the tool's function: 'Filter tickets using Freshservice query language.' This distinct verb+resource pairing differentiates it from sibling tools like get_tickets (which likely lists without filtering) and get_ticket_by_id. The mention of the query language adds precision.

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 concrete usage context through examples such as 'status:2' and 'priority:4', which imply when to use this tool. However, it does not explicitly state when not to use it or mention alternatives like get_tickets, so it lacks explicit exclusions and alternative references.

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