get_snippet

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

With no annotations, the description must carry the behavioral burden. 'Get' does imply a read-only retrieval and 'Liquid code' describes the returned substance, but nothing is said about side effects, errors, permissions, or the exact response shape.

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 description is a single, front-loaded sentence with zero filler. Every word contributes to the agent's understanding of what the tool returns.

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?

For a simple one-parameter getter, the description and schema cover the basics. However, there are no annotations and no output schema, so the description does not disclose potential errors, permissions, or the complete response format beyond saying it is Liquid code.

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 description coverage is 100% and the single parameter snippet_id is already documented clearly. The description adds no additional parameter semantics beyond reinforcing that the ID identifies the snippet to retrieve.

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 ('Get'), a precise resource ('a specific snippet'), and the returned content type ('Liquid code'). This clearly distinguishes it from list_snippets (...) and get_template (...).

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 phrase 'a specific snippet' implies use when retrieving one snippet by ID, and list_snippets is an obvious sibling for enumeration. However, there is no explicit guidance on when not to use it or what to use instead, leaving the routing to inference.

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