list_snippets

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

No annotations provided, so the description carries full behavioral burden. It implies a read operation but does not confirm read-only safety, mention pagination, or describe what the return set looks like. For a 0-param list tool with no annotations, this is thin.

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 that is front-loaded and wastes no words. However, it is arguably too terse given the lack of other descriptive context.

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?

An output schema exists, so return values need not be explained. But with no annotations and no usage context, the description is barely adequate. It tells the agent what the tool does but not when to use it, what the catalog scope is, or any constraints.

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?

Zero parameters required, so baseline is 4. The description does not need to explain parameter behavior, and schema coverage is 100% (empty object).

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 clear verb+resource: lists snippets from the catalog. Distinguishable from siblings like add_snippet and remove_snippet since it is a read-only list operation. However, it does not clarify scope (all snippets vs. filtered) or differentiate from other list_* tools beyond naming the resource.

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 guidance on when to use this versus alternatives. The agent gets no context on prerequisites, whether it's scoped to a session or global, or what to do if no snippets exist. Implicit usage only.

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