spidra_list_presets

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: results are ordered newest first, two preset subtypes exist, and presetId switches from list mode to single-record mode.

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 short sentences, no filler, with the core listing behavior front-loaded and the presetId and run alternatives following naturally. Every sentence carries information an agent needs.

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?

For a read-only list tool with no output schema, the description covers what is returned, the ordering, and the single-item mode. Pagination defaults live in the schema, so the only minor gap is any description of response shape, which is acceptable here.

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%, so page and limit are fully documented in the schema and the description need not repeat them. The description reinforces presetId's dual meaning, but that is already stated in the schema, so it adds no new semantic detail.

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 and resource (list the user's saved presets) plus ordering and scope (newest first), and explicitly enumerates what a preset is: saved template runs and saved tool requests. This clearly distinguishes it from siblings like spidra_run_preset, spidra_save_preset, and spidra_delete_preset.

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?

It explains the presetId branch (fetch one preset in full instead of listing) and explicitly routes execution to spidra_run_preset. There is no explicit 'when not to use' guidance, but the alternatives that matter are named.

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