list_snippets

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

Describes search behavior (substring, case-insensitive) and return format with specific keys. No annotations provided, so description carries full burden; covers query characteristics and output structure adequately.

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 sentences, front-loaded with purpose. Every sentence provides value: tool purpose, parameter behavior, return structure, sibling reference. No redundant text.

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?

Fully covers purpose, parameter usage, return shape, and relationship with sibling. Given simple input schema and no output schema, description leaves no gaps for an agent to invoke correctly.

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 sole parameter 'search' is explained: 'filters by any substring of the key or name (case-insensitive)'. Schema has 0% description coverage, so this adds essential meaning beyond 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?

Clearly states 'List available website building-block snippets' with a specific verb and resource. Distinguishes from sibling 'get_snippet' by positioning this as the listing tool.

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?

Explicitly explains when to use (list all or filter) and directs to 'get_snippet(key)' for fetching injectable HTML, providing clear alternative.

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