plugins

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

With no annotations, the description carries full burden but only discloses basic listing behavior. It omits behavioral traits like authentication requirements, rate limits, or effects of parameters (e.g., filter, versions).

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?

Single sentence is efficient but under-informative. While no wasted words, it could be expanded with crucial parameter context without becoming verbose.

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?

Given 4 parameters and no output schema, the description is incomplete. It fails to specify return format (though format param exists), what constitutes 'installed plugins', or how filter and versions affect results.

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 low (25% for vault only), and the description adds no parameter explanations. The meaning of 'filter', 'versions', and 'format' remains implied by schemas, requiring agent inference.

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?

The description 'List installed plugins.' clearly states the verb (list) and resource (installed plugins), distinguishing it from siblings like 'plugin' (singular) and 'plugins_enabled' (which likely filters by enabled status).

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?

No guidance on when to use this tool versus alternatives. For example, it does not differentiate from 'plugins_enabled' or explain that 'plugin' is for a specific plugin. No when/when-not context.

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