List plugins

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

Annotations (readOnlyHint, openWorldHint, idempotentHint) already cover safety and side-effect expectations. The description adds the per-profile scoping ('on a profile') but does not disclose further behavior such as whether disabled plugins are included, result ordering, or pagination. No contradiction with annotations.

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 sentence containing the essential components—verb, resource, and scope—with no unnecessary words or structure. It is appropriately front-loaded.

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 the tool's simplicity (one optional parameter, no output schema, no nested objects), the description is sufficient for an agent to understand what it does. It does not describe the return format, but for a list operation this is a minor omission given the straightforward nature.

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?

There is one parameter, profile_id, with no schema description (0% coverage). The phrase 'on a profile' implies the parameter selects the profile, and the schema provides default, min, and max. This is adequate for a simple integer ID but the description does not explicitly explain the parameter.

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 states a specific verb ('List'), resource ('plugins'), and scope ('installed on a profile'). This clearly differentiates it from sibling tools like nuvio_add_plugin, nuvio_toggle_plugin, nuvio_reorder_plugins, and nuvio_remove_plugin.

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 guidance on when to use this tool versus the many plugin-related siblings. The agent must infer that this is the read operation among plugin management tools; no explicit exclusions or alternative conditions are given.

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