storage_list

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

No annotations provided, so description carries full burden. Discloses scroll session expiry (15s inactivity) and max 1000 per call. Implies read-only nature (listing RIDs). Could mention rate limits or error scenarios, but covers key behaviors.

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: first states purpose, second adds key behavioral constraints (scroll expiry, limit). No redundancy, every word earns its place.

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?

No output schema, so description must clarify response format. It mentions listing RIDs and scroll pagination but does not specify whether response includes a scroll_id or other fields. Incomplete for a tool with 5 parameters and no output schema.

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%, so baseline is 3. The description adds value by mentioning scroll session expiry and max return limit, which are not in parameter descriptions. Provides behavioral context over schema alone.

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 it lists RIDs of stored crawled pages with store=true, using specific verbs and resource naming. Distinct from sibling storage_get (single) and storage_count (count). Includes scroll pagination and limit details.

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?

Describes what the tool does but does not explicitly guide when to use it over alternatives like storage_get or storage_count. Agent must infer usage context from sibling names. Lacks 'when-not-to-use' or explicit differentiation.

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