check_disk_usage

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

No annotations exist; the description is minimal and doesn't disclose operational traits like requiring root, output format, or potential performance impact on large directories.

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?

Single sentence of 11 words, no redundancy. Front-loaded with verb and object.

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 tool, the description is adequate but omits return format and behavioral details. Agent would need to infer output from 'show disk usage'.

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 is 50% (path has description, alias does not). The description adds context about 'all mounts' vs 'specific directory', which aligns with the path parameter default '/'. However, it doesn't clarify alias usage or add significant meaning beyond schema.

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 shows disk usage for a directory or all mounts. It distinguishes from siblings like 'system_info' or 'list_directory' by focusing on disk space, but doesn't explicitly contrast with alternatives.

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 vs. other tools. Siblings like 'system_info' or 'list_directory' exist but no exclusions or context provided.

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