list_skills_and_plugins

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

With no annotations at all, the description carries the full burden of behavioral disclosure and falls short. It hints at an index ("indexed") but does not say whether results are ranked, whether an empty query lists everything, how many results come back, or whether the operation is read-only in any sense beyond the verb.

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?

One short sentence with no filler, and the resource scope is front-loaded. Its terseness is efficient rather than padded, though it borders on being too short to be actionable.

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 presence of an output schema excuses not documenting return values, but the definition still omits when to call it, what the query does, and how the index behaves. For a zero-annotation, zero-schema-coverage search tool, that leaves meaningful gaps.

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 single `query` parameter has 0% schema description coverage (only a string type and an empty-string default), and the description never mentions it. It therefore does not clarify whether an empty default means "list all" or "no results", nor whether matching is substring, keyword, or semantic over the indexed content.

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 names a specific verb ("Search") and concrete resources ("indexed SKILL.md files and MCP/plugin manifests"), which is enough to separate it from the harness/model/task siblings. The one weakness is the mismatch with the tool name "list_skills_and_plugins", so an agent cannot tell from the name alone whether this enumerates or searches.

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 when-to-use guidance, no mention of when not to use it, and no named alternative. The description never explains the relationship to discovery siblings such as discover_harness_models or get_integration_status, so the agent must infer the choice from resource vocabulary.

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