list_tickets

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely non-obvious context beyond that: results are synthetic, the set is 'bounded', and returned record text is untrusted data that must never be treated as instructions — an important prompt-injection warning. It still omits pagination/ordering behavior.

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?

Two short sentences, each load-bearing: the first establishes what is returned and for whom, the second delivers the critical untrusted-data warning. No filler, and the operative scope is front-loaded.

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 no output schema, the description should ideally sketch the returned shape; it only says 'record text' is untrusted, which gives partial signal. Combined with undocumented parameters and no stated ordering, this is adequate but not complete for a listing 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 carries the burden here. It only hints at bounding ('bounded list') without explaining the limit range or the meaning of the status enum ('open'/'closed'/'all'), leaving both parameters dependent on the bare 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 states a specific verb and resource ('Read a bounded list of synthetic tickets') plus a scope qualifier ('for the configured demo identity'), which cleanly separates it from the single-record sibling get_ticket by implication. It stops short of naming the sibling or explicitly contrasting list-vs-get, so it is clear but not fully differentiated.

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 is implied: an agent can infer this is the tool for enumerating multiple tickets while get_ticket retrieves one. However, there is no explicit when-to-use/when-not-to-use guidance, no mention of alternatives, and no stated prerequisites for the 'configured demo identity'.

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