get_prompt

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

With no annotations provided, the description carries the burden and covers the key behavior: it returns the record or an explicit not_found error object. This makes the tool's behavior predictable for an agent without over-explaining.

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 short sentences carry the entire necessary message: what is fetched, how to obtain the id, and the error behavior. There is no filler or redundant restating of the tool name.

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?

The tool has a single required parameter, an output schema, and a clear error contract. The description fully covers the retrieval path and failure mode, leaving no important gap for an agent to guess.

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 input schema only declares id as a string with no description. The tool description adds crucial meaning by specifying that the id is the id field of any record returned by list_prompts or search_prompts, telling the agent exactly where a valid value comes from.

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 uses a specific verb and resource: 'Fetch one captured prompt by its id.' It clearly distinguishes this single-record getter from the list/search siblings by emphasizing retrieval by id.

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?

It explicitly connects this tool to list_prompts and search_prompts by noting that the id comes from records returned by those tools. This gives clear context for when to use it, though it does not explicitly state exclusions like 'do not use for listing or searching.'

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