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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: results are slugs only, not full command content, requiring a follow-up get_command call — important since no output schema exists. It stops short of mentioning result caps or pagination behavior.

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?

Two tight sentences, zero waste. The scope statement is front-loaded and the downstream-call hint follows immediately, so an agent gets purpose and next step in one pass.

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?

With no output schema, the description correctly carries the burden of stating what comes back (slugs). All parameters are optional, so no required-arg gaps exist. Missing only sorting/pagination expectations and when to prefer trending_commands, which leaves a small but real 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?

Schema coverage is 67%, with tag, kind, and query documented inline, while sort and limit have no descriptions. The tool description adds no parameter-level meaning (e.g., how tag/kind/query combine, or that limit caps at 25), so it neither compensates for the gaps nor adds over the schema.

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?

States a specific verb and resource ('Search CommandVault's library of AI commands') and enumerates the concrete artifact types covered (prompts, CLAUDE.md templates, Cursor rules, slash commands, subagents). It also distinguishes itself from the retrieval sibling by noting it returns slugs to pass to get_command.

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 establishes the search-then-fetch workflow with get_command, which is a real usage cue. However, it gives no guidance on when to use this versus siblings like trending_commands, list_collections, or list_communities, and no exclusions or preconditions are stated.

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