plugins_list

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

readOnlyHint=true already declares the safety profile, so the description's burden is lighter. It adds a useful conditional note that the ui listing only maps to deletable IDs "when writes are enabled", but says nothing about the with_data payload cost or result size, which matters for a listing call that can embed archive data.

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?

One front-loaded sentence with no filler; the filter semantics come first and the cross-references follow. The trailing "use jobs_list for jobs" clause is slightly tangential but earns its place as disambiguation.

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 two-parameter, fully documented, read-only list tool with no output schema, this covers what an agent needs to invoke it correctly. Minor gaps remain around the shape/cost of results when with_data is true, but the schema carries the parameter meaning.

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 100%, so the baseline is 3; the description goes slightly beyond by giving type=ui a downstream meaning (IDs accepted by plugin_delete) rather than just an enum label. The with_data parameter is left entirely to the schema, which is acceptable given full coverage.

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?

Specific verb+resource ("List installed plugins") plus the filter dimension (all, external, ui, pro). It also names the sibling it is not ("use jobs_list for jobs") and cross-references plugin_delete, so an agent can place it in the toolset without opening the 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 selection rule for the type parameter (type=ui → IDs accepted by plugin_delete when writes are enabled) and redirects to jobs_list for jobs. It lacks an explicit statement of when not to call it, but the routing context is clear enough to act on.

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