list_open_tickets

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

No annotations exist, so the description carries the full disclosure burden. It does reveal non-obvious behavior: only open tickets are returned, results are urgency-sorted, and the result size is capped (limit max 25). But it never states that the operation is read-only or non-mutating, and it says nothing about empty results, errors, or authorization requirements. The disclosure is adequate but not rich.

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 prose is tight and front-loaded — the first sentence states the core purpose, the second flags the filter. The embedded JSON is bulky and contains redundant structure (the anyOf wrapping with null), but since the real input schema documents nothing, it earns its place as the sole source of parameter semantics.

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?

An output schema exists, so describing return values is not required. The description covers what is listed, the ordering, the filter options, and the limit constraints — enough for an agent to construct a correct call. The gaps are the missing usage-vs-alternative guidance and the lack of an explicit read-only confirmation, but the essential call contract is documented.

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% — the input schema is a generic 'arguments' envelope with no property-level documentation. The description compensates by embedding the full parameter specification: the priority enum values (low, medium, high, urgent) with null default, and limit with default 10, minimum 1, maximum 25. It loses only stylistic points for delivering this as a raw JSON dump with redundant anyOf-null structure rather than clean prose.

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 opens with a specific verb-resource pair ('List open support tickets') and adds a scope qualifier ('open') plus an ordering guarantee ('most urgent first'). This is unambiguous even without reading the schema, and nothing among the siblings (get_deal, list_deals, update_deal_stage, etc.) overlaps with listing tickets. It does not explicitly name a sibling to distinguish itself from, which keeps it just shy of a 5.

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?

Usage context is implied rather than stated: the 'open' scope and 'most urgent first' ordering tell an agent what kind of query this serves, and 'Optional priority filter' hints at how to narrow it. However, there is no explicit when-to-use versus when-not-to-use guidance, no mention of alternatives, and no exclusions (e.g., closed tickets are out of scope but that is only inferred).

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