storage_read

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

Adds beyond annotations: describes timeout caveat, text vs binary behavior, 8KB cap, example path, and read-only nature. No contradiction with readOnlyHint 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?

Three front-loaded sentences covering action, return types, example, and a crucial warning. No redundant information; every sentence serves a purpose.

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?

Given one parameter, output schema existence, and moderate complexity, the description covers tool purpose, usage context, limitations, and format details comprehensively.

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 has 0% coverage for path parameter, but description compensates with a concrete example and format explanation. Could add more detail on length or allowed characters, but sufficient for usage.

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 the tool reads files from Flipper storage over BLE, describes supported text formats and binary fallback, and distinguishes from sibling write/delete tools by emphasizing read-only nature.

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 warns about BLE timeout on large files and directs to USB-based alternative `flipper` server's storage_read, providing clear when-not-to-use guidance.

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