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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered; the description adds value by enumerating the returned fields and the possible status values (open, closed, scheduled, archived), which is the kind of read-shape detail annotations cannot convey. It does not discuss the cursor pagination contract or rate limits, but the schema documents the cursor.

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?

Three compact, front-loaded clauses: what it lists and returns, how the output is used, and the endpoint. No filler and no restatement of the title.

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 7 optional params and no output schema, the description compensates by naming the fields returned and the status enum, and it points to the endpoint. The only gaps are that pagination and the filter parameters are left entirely to the schema; nothing an agent needs in order to call it correctly is missing.

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 100%, including enum values for sort, limit bounds and the starting_after cursor contract, so the description has little left to explain. Its mention of created and updated dates loosely gestures at the date-range filters but adds no syntax or timezone guidance beyond the schema. Baseline 3 is appropriate here.

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?

States a specific verb (List) and resource (the account's TicketSpice forms), and immediately disambiguates the vendor's jargon by equating 'forms' with 'ticketed events / order pages'. It also names the returned fields and the underlying endpoint (GET /forms), so an agent can separate it from the singular ticketspice_get_form without opening a schema.

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?

Gives a concrete downstream reason to call it: 'Use the form ids to filter orders, tickets and transactions,' which tells the agent this is the discovery step before order/ticket listing. It stops short of explicitly naming alternatives (get_form for a single form) or stating when-not to use it, so it is clear context without exclusions.

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