get_stored_response_with_markdown

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 covers the main operation, supported formats, and a timeout caveat for large PDFs, but it does not mention potential side effects, error cases, or whether the operation is strictly read-only.

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 concise and well-structured, with a clear two-sentence explanation plus a useful timeout note. No unnecessary words or repetition are present.

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 description gives enough context for a simple retrieval-and-convert tool: what it does, the supported formats, and a practical timeout warning. It lacks explicit error behavior details, but the main use case is adequately covered for an agent to call it correctly.

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 already describes response_id as 'ID of the stored response', and the tool description only repeats 'by its ID'. No additional meaning is added beyond the schema, so the baseline score applies.

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 identifies the action: retrieving a stored HTTP response by ID and converting it to Markdown. It also specifies supported content types (HTML, PDF), making the tool's purpose distinct from the sibling get_stored_response.

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 usage for retrieving stored responses and converting them to Markdown, and it mentions HTML/PDF support. However, it does not explicitly state when to prefer this tool over the sibling get_stored_response or other HTTP tools, leaving the choice somewhat implied.

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