uad_list_plugins

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

No annotations are provided, so the description carries the burden. The verb 'List' implies a read-only operation, and it adds useful behavioral context: 'Filterable and limited by default.' It does not explicitly state non-modifying behavior or connection requirements, but for a catalog listing tool these are largely entailed.

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?

The description is extremely concise and well-structured: it opens with the action and purpose, then provides usage guidance and an explicit exclusion. Every sentence adds value with no redundancy.

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?

The description covers the tool's purpose, output content, filtering behavior, and typical use cases, and it distinguishes the tool from its closest sibling. Because an output schema exists, detailed return values are not necessary. A minor gap is the lack of explanation about how filtering parameters interact, but overall this is adequate.

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%, and the description does not explain the five parameters (limit, search, category, unison_only, authorized_only) beyond the generic statement 'Filterable and limited by default.' The parameter names are somewhat intuitive, but the description does not compensate for the lack of schema descriptions.

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 clearly states the tool lists the installed UAD plugin catalog with specific output fields (name, categories, Unison capability, authorization status). It also explicitly distinguishes itself from uad_get_inserts, which lists currently loaded plugins.

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?

The description gives explicit use cases: 'Use when: choosing a plugin to load, or checking whether one is authorized.' It also names a specific exclusion: 'Not for: what is currently loaded on channels - that is uad_get_inserts.'

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