Search FreeScout Tickets

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

The description explains that includeLastMessage gives a preview of the most recent message, which is a behavioral trait. However, it does not mention that the tool is read-only or non-destructive, and since no annotations are provided, the description should carry more weight for safety disclosure.

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 concise at two sentences, with the first sentence stating the purpose and the second providing key parameter details. There is no fluff, but it could be better structured with bullet points for readability.

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 10 parameters, no output schema, and no annotations, the description lacks completeness. It fails to describe most parameters, does not explain the return format (e.g., pagination, fields), and omits any mention of error behavior or limits. Significant information is missing for an agent to use the tool effectively.

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?

With 0% schema description coverage, the description adds meaning for assignee (unassigned, number), time filters (relative formats), and includeLastMessage. However, 7 of 10 parameters (page, pageSize, state, status, mailboxId, textSearch, createdSince, updatedSince) are not explained, leaving significant gaps.

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 'Search for FreeScout tickets' with specific verb and resource, and provides examples of filter parameters. However, it does not explicitly distinguish this tool from the sibling 'freescout_get_ticket' for retrieving a single ticket, which would improve clarity.

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 gives usage details for parameters like assignee and time filters, but provides no guidance on when to use this search tool versus the sibling tools (e.g., get_ticket). There is no explicit when-to-use or when-not-to-use advice, which is a significant gap.

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