list_entries

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

The description discloses tags use OR match, but lacks mention of pagination, limits, or default behavior when no filters applied. Without annotations, more behavioral details would be beneficial.

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?

Short and front-loaded: the main action in the first sentence, followed by a clean list of filter options. Each sentence serves a purpose with no wasted words.

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 tool has an output schema (not shown), so return values are not needed. The description covers filters and tag logic, but pagination info is missing. Overall, fairly complete for a listing tool with 3 optional params.

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 coverage is 0%, yet the description adds meaning by listing possible values for type (skill, agent, command, hook), examples for plugin (android, delivery, research-suite), and clarifying tag matching logic. This compensates well for the schema gap.

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 'List all registry entries' with specific filter options (type, plugin, tags), distinguishing it from siblings like list_plugins (only plugins) and search_entries (likely more advanced).

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 explicit guidance on when to use list_entries versus alternatives such as search_entries, get_entry, or list_plugins. The description only explains how to filter but not when to choose this tool.

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