storage_get

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

Describes core behavior: retrieval method, precondition, and return format options (as=html returns body, as=markdown converts). No annotations exist, so the description carries the full burden, which it meets for a non-destructive retrieval 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 that efficiently convey purpose, precondition, and key parameter behavior. No redundant information; every word contributes to clarity.

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?

Fully covers what the tool does, when it applies, what it returns, and how to modify output format. No output schema exists, but description sufficiently explains return value. No gaps for a simple retrieval tool.

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%, but the description adds value beyond the schema by explaining the effect of the 'as' parameter ('return just the body' for html, 'convert it' for markdown). For rid and url, description reinforces schema hints. No extra for use_js_token, but schema already covers it.

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?

Clearly states 'Retrieve a single stored page' with specific verb and resource, specifies identification by RID or URL, and includes precondition (previously crawled with store=true). Distinguishes from sibling tools like storage_list or storage_bulk_get.

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 states the precondition for use ('Only works for pages previously crawled with store=true'), providing clear context. Does not explicitly mention alternatives or when not to use, but the precondition effectively limits appropriate contexts.

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