get_disk_space

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

No annotations are provided, so the description carries full burden. It states that the tool returns disk space info (total, used, free) but does not explicitly confirm it is read-only or disclose any potential side effects. The description is adequate but lacks explicit behavioral transparency beyond what is implied.

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, using a single line of purpose, a code example, and a one-line output summary. The example is helpful but could be shortened. No unnecessary words; front-loaded with purpose. Slight room for improvement in integration.

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 no output schema, the description outlines the return shape (total, used, free) but lacks details on key names, error behavior, or handling of invalid drives. It covers the main use case but is not exhaustive for a tool with potential edge cases.

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 100%, so baseline is 3. The description adds value by explaining that omitting the 'drive' parameter returns all drives, and includes an example showing default unit 'GB'. This clarifies parameter usage beyond the schema's enum/type descriptions.

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's purpose: 'Get disk space information for all drives or specific drive.' It uses a specific verb ('Get') and resource ('disk space information'), and distinguishes from siblings like get_cpu_usage or list_processes, which cover different system metrics.

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 provides an example usage but does not explicitly state when to use this tool versus alternatives. However, given that sibling tools cover different domains (SSH, security, commands), the purpose is clear enough to infer appropriate usage. No explicit exclusion or alternative guidance is given.

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