flipper_storage_space

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

With no annotations, the description carries the full burden. It discloses that this is a read operation ('Get') and indicates the returned data type (bytes), which is useful. However, it does not detail error handling, exact return structure, or behavior for invalid paths, though these are relatively minor for a simple query 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?

The description is a single sentence that is front-loaded with the action and resource, containing no filler or redundant details. It immediately states what the tool does and for which filesystems, making it maximally efficient.

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 its simplicity—one parameter, no output schema, no annotations—the description covers the essential aspects: purpose, valid inputs, and output type (total/free bytes). It lacks details on exact return fields or error conditions, but the tool is cross-referenced among many siblings and its behavior is straightforward, so the description is sufficiently complete for correct invocation.

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 has one parameter 'path' with 0% description coverage. The description compensates fully by explaining valid values: '/ext (SD)' and '/int (flash)'. This gives the agent the necessary meaning to pass the correct path, exceeding the schema's bare/default information.

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 states the tool's purpose with a specific verb ('Get') and resource ('total and free bytes' for the '/ext' or '/int' filesystem). It distinguishes itself from siblings like flipper_stat or flipper_list_dir by focusing on storage capacity rather than file 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?

The description provides clear context by specifying the target filesystems (/ext or /int) and the metric retrieved (total/free bytes), making the use case obvious. It does not mention explicit alternatives or exclusions, but no direct sibling serves the same purpose, so the guidance is adequate.

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