list_plugins

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

No annotations are provided, and the description does not disclose behavioral traits like read-only nature, permissions, or side effects. It assumes the tool is a safe listing operation but fails to confirm this, leaving the agent with incomplete information.

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 a single, front-loaded sentence that concisely captures the tool's function and key usage. Every word serves a purpose, with no unnecessary elaboration.

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 simple list tool with two parameters and no output schema, the description adequately covers the functionality. It could mention the return type is a list of plugins, but this is implicit and not a critical gap.

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?

With 50% schema description coverage, the description adds value by mentioning both parameters as filters. However, it does not fully explain the boolean 'installed_only' parameter, leaving ambiguity about its exact meaning (e.g., whether it shows only installed or only store plugins).

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 Blockbench plugins, both installed and from the store, with filtering options. It uses specific verb 'list' and resource 'plugins', distinguishing it from action-oriented siblings like install_plugin or uninstall_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?

The description provides clear context for when to use the tool: when listing plugins with optional filtering. It does not explicitly mention when not to use it or alternatives, but the purpose is well-defined and the filtering guidance is helpful.

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