cat_plugins

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

No annotations are provided, so the description carries full burden. While '获取已安装的插件列表' implies a read-only operation, it doesn't disclose any behavioral traits like whether this requires special permissions, what format the output takes, if there are rate limits, or how comprehensive the list is. For a tool with zero annotation coverage, this is insufficient disclosure.

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, efficient Chinese sentence that directly states what the tool does. It's appropriately sized for a simple listing tool with no parameters. Every word earns its place - there's no wasted verbiage or 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 read-only listing tool with no parameters and no output schema, the description is minimally adequate. It tells you what the tool does but doesn't provide context about the output format, potential limitations, or how it fits with sibling tools. Without annotations or output schema, the description should ideally provide more behavioral context.

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?

The tool has 0 parameters with 100% schema description coverage. The description doesn't need to explain any parameters since there are none. The baseline for 0 parameters is 4, as the description appropriately doesn't waste space discussing non-existent parameters.

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 purpose: retrieving a list of installed plugins. It uses a specific verb ('获取' - get/retrieve) and resource ('已安装的插件列表' - installed plugins list). However, it doesn't explicitly differentiate from sibling tools like 'cat_aliases', 'cat_indices', or other 'cat_' tools that also list different types of information.

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 no guidance on when to use this tool versus alternatives. There are many other 'cat_' tools in the sibling list (cat_aliases, cat_indices, cat_nodes, etc.) that serve similar listing purposes for different resources, but the description doesn't indicate this is specifically for plugins or when you'd choose this over other listing tools.

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