get_disk_usage

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

The description discloses that it is a read-only operation with no side effects and that partitions requiring elevated privileges are silently skipped. Since no annotations are provided, the description fully covers behavioral traits.

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 concise (5 sentences), front-loads the main purpose, and every sentence adds value: purpose, usage, safety, output format, and edge case. No superfluous text.

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 no parameters and no output schema, the description covers the tool completely: what it does, when to use, what it returns (Markdown table columns and I/O stats), and a behavioral note. No gaps.

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 tool has zero parameters and schema description coverage is 100%. The description need not add parameter information. Baseline 4 is appropriate.

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 states 'Show detailed disk usage for all mounted partitions with I/O statistics,' which is a specific verb+resource+scope. It also distinguishes itself from the sibling tool get_system_overview by noting it provides 'detailed' info vs a 'quick summary.'

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?

Explicit usage context: 'Use this for disk space analysis... For a quick disk summary... use get_system_overview instead.' This provides clear when-to-use and when-not-to-use guidance with a named alternative.

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