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

The annotation readOnlyHint=true already indicates this is a safe read operation, and the description adds 'public organic' and 'exact AI-search question' as additional context. But it does not disclose other behavioral traits such as return format, error handling, or pagination, making this a modest contribution beyond the annotation.

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 sentence that front-loads the verb 'Fetch' and immediately states the resource and condition. It is concise with no wasted words, fitting the purpose perfectly.

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 single-parameter read tool, the description provides sufficient purpose but lacks details about the response content, limitations, or parameter semantics. With no output schema, a bit more explanation of what 'prompt detail' includes would improve completeness.

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 schema has 0% description coverage for the single 'slug' parameter. The description only repeats that the fetch is 'by slug' and does not explain what a slug is, its format, or any constraints. This gives minimal semantic value beyond the schema itself.

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 action ('Fetch one public organic prompt by slug') and a purpose ('inspect the exact AI-search question behind a result'). It clearly identifies the resource (prompt) and scope (public organic, by slug), but does not explicitly differentiate from sibling tools like parse_get_stats or parse_search.

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 includes a clear usage context ('when the user wants to inspect the exact AI-search question behind a result'), which tells when to use this tool. However, it does not mention when not to use it or suggest alternatives, so it falls slightly short of a 5.

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