read_latest

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

Description adds 'newest by timestamp', 'decoded text or a binary summary', and 'over BLE' beyond the annotations. No contradiction with readOnlyHint=true; both say 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?

Two sentences, front-loaded with core purpose, no fluff. Every sentence provides value.

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 low parameter count and output schema existence, description covers tool purpose, parameter meaning, return type, and usage context thoroughly.

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 0%, but description adds meaning by listing example folder paths ('/ext/nfc', '/ext/subghz', etc.) and explaining its role as the directory to search for the latest file.

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?

Description clearly states it reads the most-recently-saved file in a Flipper folder over BLE, with specific examples like NFC, Sub-GHz, RFID. It distinguishes from siblings like storage_read by emphasizing 'latest' and 'newest by timestamp.'

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?

Provides context for when to use: 'pull the NFC card / Sub-GHz capture / RFID dump you just saved on the device.' Does not explicitly state when not to use or name alternatives, but the context is clear enough.

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