plugin_list_presets

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

Annotations already declare readOnly/idempotent/non-destructive, so 'Read-only.' is largely redundant. However, the description adds real behavioral detail beyond the annotations: pagination via next_start, that preset_count is authoritative, and that the current preset index is returned only when unique, plus the include_current opt-out.

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 paragraphs, front-loaded with what is read and immediately followed by read-only status, pagination behavior, and routing. Every sentence carries information an agent needs; the only near-redundancy is the terse 'Read-only.' line.

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 paginated read tool with an output schema, this is complete: it names the payload shape (count, page of indexed names, next_start, current preset), the paging mechanism, and the follow-up tool. Nothing required to invoke or continue the operation 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%, so the baseline is 3 and the schema already explains limit, start, include_current, and include_empty_names. The description adds a little interpretive value by clarifying what include_current=false suppresses and by introducing the next_start pagination contract that links the page parameters to the response.

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+resource and scope: 'Read a page of a loaded plug-in's preset names, its preset count, and current preset.' It is clearly separable from siblings like plugin_list_loaded (which enumerates plug-ins) and plugin_list_parameters (which enumerates parameters), so an agent can pick it without opening any 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?

Explicitly routes the agent: 'Use a name or index from this list with plugin_select_preset; use sound_plan_palette to choose sounds across several roles.' The schema description further points to plugin_list_loaded for obtaining valid targets, covering the prerequisite step as well as the successor.

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