show_disk_manager

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

Discloses auto-scanning and chart display. No annotations provided, but could mention if scanning takes time or if it's read-only. Slight gap.

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?

Two concise sentences plus usage tip, no fluff, key information upfront.

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 screen-opening tool with no output schema, it sufficiently describes what user sees (charts, breakdown).

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?

No parameters, so no need for explanation. Description adds context about auto-scanning beyond the empty 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 action (open screen, auto-scan) and resource (Disk Manager). It distinguishes from sibling tools by emphasizing visual output over data retrieval.

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?

Explicitly specifies when to use: when user wants to SEE disk usage or for first-time demos, implying alternatives like get_storage_breakdown for data.

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