Library Storage Stats

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

No annotations provided, so description carries full burden. It only says 'summarize storage usage' but does not disclose behavioral traits like read-only nature, auth requirements, or whether it returns aggregated or raw data. Minimal disclosure.

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?

Extremely short (4 words) but under-specified. While concise, it sacrifices necessary information for usability. Every sentence should add value; this description lacks context and structure.

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?

With 11 parameters, no output schema, and many siblings, the description is highly incomplete. It does not explain the summary output, parameter roles, or differentiate from similar tools. Lacks essential context 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?

Schema description coverage is 0% and description adds no meaning to any of the 11 parameters. Parameters like 'to', 'app', 'from', 'page', 'cursor', 'detail', etc., are completely unexplained. The description fails to compensate for schema coverage deficit.

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 verb 'summarize' and resource 'storage usage by library'. It distinguishes from siblings like storage_by_codec or storage_by_quality by focusing on library-level aggregation rather than breakdowns. However, it could be more specific about what 'summarize' entails.

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?

No guidance on when to use this tool vs alternatives such as library_summary, storage_usage, or other storage breakdown tools. The description lacks context for appropriate usage.

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