list_track_plugins

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

The annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is fully covered. The description adds one genuinely useful behavioral claim, that processor IDs are stable (usable as durable references across calls), but gives nothing about ordering, page-size ceilings, or the meaning of dry_run/confirm_delete/expected_revision that appear in the schema. With annotations carrying the safety story, a 3 fits.

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?

A single eight-word sentence with no filler and the resource stated up front. It is efficiently written, though the terseness is part of why the parameter and usage gaps exist rather than a sign of tight, complete messaging.

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-value detail is fairly excused, but the input side is a required nested object with seven undocumented fields, several of which imply mutation or concurrency semantics on a tool flagged read-only. For that complexity level, one sentence about pagination and ID stability leaves the agent without enough to call it correctly or interpret the schema.

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% across seven nested properties (track_id, limit, offset, name_filter, dry_run, confirm_delete, expected_revision), and the description documents none of them. "Paginate" weakly implies limit/offset exist, but the surprising fields for a read-only tool — confirm_delete, dry_run, expected_revision — are left entirely unexplained. The description does not compensate for the coverage gap.

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?

"Paginate plugin instances" gives a read/list verb and a resource, and "stable processor IDs" hints at what comes back. However, it never states the track scoping that the name and the required track_id parameter imply, and it does not distinguish this from siblings like list_available_plugins or list_plugin_presets. An agent has to infer the key qualifier from the tool name rather than the description.

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 when-to-use guidance at all: no statement of the situation that selects this tool over list_available_plugins or list_plugin_presets, and no prerequisites or exclusions. The only steer is the word "Paginate," which implies a large result set but gives no threshold or alternative for non-paginated access.

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