list_snippets

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

With no annotations, the description carries the burden of explaining behavior. It discloses the listing behavior and category grouping, but does not mention return format, ordering, category semantics, or any read-only/authorization implications. This is acceptable for a simple list tool but not richly transparent.

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?

The entire description is a single, concise sentence that conveys both the action and the organizing principle. There is no filler or repetition, and the core purpose is front-loaded.

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?

Given the tool's low complexity (zero parameters, no output schema, straightforward listing behavior), the description is nearly complete. It tells the agent what the tool returns and how it is organized. It could mention expected output shape or category sources, but these are not essential for invoking a no-argument list tool.

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 tool has zero parameters, so there is no parameter semantics for the description to clarify. The baseline of 4 applies because the description does not need to compensate for undocumented parameters; its 'por categoria' note provides useful contextual meaning not captured by the empty 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?

The description states a specific verb and resource: 'Lista todos os snippets disponiveis' (lists all available snippets). It also adds scope and organization with 'por categoria' (by category). This clearly distinguishes it from siblings like search_snippets, which imply filtering or querying rather than listing everything.

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 implies the tool should be used when an agent needs an overview of all available snippets grouped by category. However, it does not explicitly contrast with alternatives such as search_snippets or get_snippet, nor does it state when not to use it, so some inference is required.

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