snapshot_disk_usage

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It clearly indicates the tool reports/reads disk usage, which implies a non-destructive operation, but it does not explicitly state that it makes no modifications, nor does it mention any operational caveats, environment dependencies, or output behavior beyond the listed metrics.

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 first sentence is concise, front-loaded, and informative. However, the second sentence is a broad 'Snapshot guide' listing many sibling tools, which is not directly about invoking snapshot_disk_usage and largely duplicates information already available in the sibling tool list, adding noise.

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?

The description covers the tool's purpose, the resource it inspects, and the main categories of returned information. With only one optional, fully documented parameter and no required parameters, an agent has enough context to call it correctly. It does not detail exact output structure for json mode, but the metric list provides adequate guidance.

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 100% and the single response_format parameter is fully described inline with its enum values and default. The description adds no additional parameter meaning, but none is needed because the schema already documents it thoroughly.

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 states a specific verb ('Report disk usage') and resource ('snapshot directory'), and enumerates the concrete outputs: total size, file count, per-playlist breakdown, and largest files. This clearly distinguishes it from snapshot creation, listing, diffing, and restore tools in the same family.

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 explicit guidance on when to use this tool versus alternatives. The 'Snapshot guide' sentence lists sibling snapshot tools but does not explain when disk usage reporting is appropriate or when another snapshot utility should be chosen instead.

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