snipe_list

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

With no annotations, the description carries the full behavioral burden and supplies almost none: no statement that this is a read-only operation, no ordering or pagination behavior despite a limit parameter, and no mention of what the default (unfiltered) result looks like.

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?

Very compact and front-loaded, with each fragment attached to a parameter rather than padding. The telegraphic style costs a little clarity but no sentence is wasted.

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 return values need not be described, and three of four parameters are covered well. Still missing for a listing tool with a limit parameter: ordering, default result set, and pagination expectations.

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 coverage is 0% — the schema only carries titles and defaults — yet the description supplies the allowed values for kind, state, and priority (including the exact state and priority tokens), which is meaning the agent cannot get from the schema. Only limit remains undocumented, keeping it short of a 5.

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?

It states the verb and a generic resource ("List records"), then enumerates filter dimensions, so the agent knows it retrieves snipe records with filters. However "records" is vague and nothing distinguishes it from the many sibling listing tools (snipe_board, snipe_item, findings), leaving sibling selection to inference.

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?

There is no statement of when to use this over snipe_board, snipe_item, or next_snipe, and no prerequisites or exclusions. The filter values imply filtered listing but give no guidance on choosing this tool.

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