get_disk_health

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

No annotations are provided; the description indicates a read operation ('Get') and lists outputs. It does not disclose permissions, error behavior, or potential side effects, but the 'Get' prefix implies non-destructive.

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 succinct sentences: first states the purpose, second lists key return items. No unnecessary words.

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 output schema, the description explains return values. Parameter count small, schema descriptions adequate. The tool is straightforward and the description covers its role.

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 covers both parameters with descriptions (100% coverage). The description adds no additional meaning beyond what the schema provides.

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 verb 'Get' and resource 'SMART health status for a specific disk', listing specific return fields (overall health, temperature, etc.). It distinguishes from siblings like get_disk_usage and list_disks.

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 implies usage when disk health info is needed ('for a specific disk'), but does not explicitly state when not to use or mention alternatives like get_disk_usage.

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