Get Disk Space

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

No annotations present; description fails to disclose any behavioral traits such as read-only nature, auth requirements, or response behavior. The single sentence is insufficient.

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?

Extremely concise (one sentence) but lacks structure and substance. The brevity undercut by having zero useful detail beyond the tool name.

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 11 parameters, no output schema, and many sibling tools, the description is grossly incomplete. Agent cannot know how to invoke correctly.

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 has 11 parameters (1 required) with 0% description coverage. Description adds no information about parameters like 'app', 'detail', or 'cursor'. Agent has no guidance on valid values or usage.

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 the tool returns disk space information, which matches the name. However, it lacks specificity and does not differentiate from siblings like 'library_storage_stats' or 'storage_usage'.

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 tool versus similar tools like 'get_system_status' or 'storage_by_codec'. No use cases or context provided.

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