linux_disk_usage_calculator

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

Lists what the tool does but does not disclose side effects, permissions, or limitations. Since no annotations exist, the description partly fulfills transparency, but missing behavioral context like idempotency or error scenarios.

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 that quickly enumerates major capabilities and directs to describe_tool. Concise and front-loaded, but lacks structural segmentation for different functions (e.g., partition planning vs. RAID).

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?

Despite listing many features, the description omits guidance on how to invoke them (parameter usage) and does not describe return values. The complexity of the tool demands more detail than provided, even with a hint to describe_tool.

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 0% and the description does not explain the parameters (operation, input with level/diskCount/diskSizeBytes). The mapping between capabilities and required input fields is absent, forcing the agent to guess.

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?

Detailed description specifies multiple concrete operations: parsing du/df output, RAID calculations, partition planning, find query generation, and byte conversion. Clearly differentiates from sibling tools focused on other domains.

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?

Implies usage via the capability list and suggests describe_tool for full guidance, but lacks explicit when-to-use vs alternatives or exclusion criteria. No direct mention of when not to use this tool.

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