read_prompt_snippet

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

No annotations provided, but the description reveals it returns the current draft and version. The verb 'read' implies non-destructive behavior. Could mention safety, but overall transparent for a simple read tool.

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: one states purpose and content, the other gives usage guidance. No wasted words, front-loaded with key information.

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 one-parameter tool with no output schema, description covers purpose, content, and usage guidance. Could mention return format more explicitly, but sufficient for typical use.

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 100% and already describes the 'id' parameter. Description adds no additional meaning beyond 'by id,' which is implicit. Baseline score of 3 is appropriate.

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 clearly states it reads one prompt_snippet by ID, including its current draft and version. This distinguishes it from list_prompt_snippets (list) and read_prompt_snippet_published (published version).

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 advises 'Read before you update — you need the current version,' guiding the agent to use this tool before update operations. Does not explicitly state when not to use, but context provides sufficient guidance.

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