Storage Usage

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

No annotations are provided, so the description carries the burden. The explicit 'GET /sdapi/v1/storage' indicates a read-only operation, but it does not mention authentication requirements, response shape, or any side effects. This is acceptable but sparse for an unannotated 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, and includes the endpoint for precision. There is no redundant or filler content.

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?

For a simple, optional-filter stats query with high schema coverage, the description is sufficiently complete. It lacks return-value details since there is no output schema, but the tool's purpose is clear and the complexity is low.

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 input schema provides descriptions for both parameters ('types' and 'folder') with 100% coverage, so the schema already documents them. The description adds no additional semantic detail, matching the baseline for high schema coverage.

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 'Get storage folder usage stats' uses a specific verb and resource, with the endpoint clarifying it is a read-only storage statistics query. It is clearly distinct from sibling tools like memory, status, or version.

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 implies usage when storage folder usage stats are needed, but provides no explicit context, exclusions, or alternative tool references. The title and description align, making the purpose clear, but the guidance is minimal.

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