get_block_devices

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

The description mentions using lsblk -J, hinting at a read-only operation. However, it does not explicitly state if root privileges are needed or if there are side effects. Since no annotations are provided, the description carries full burden but is somewhat vague.

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 extremely concise—one sentence with no wasted words. It is front-loaded with the key purpose and method.

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 zero-parameter tool without output schema, the description is adequate but could be more complete by hinting at the JSON structure or typical use cases. It provides the core info but lacks depth.

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?

The tool has zero parameters, so baseline is 4 per guidelines. The description adds context about the underlying command (lsblk -J), which enriches understanding 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 tool retrieves block devices/partitions using lsblk with JSON output. It distinguishes from siblings like get_disk_usage by focusing on block devices specifically.

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 for listing block devices but lacks explicit guidance on when to use vs alternatives. No exclusions or when-not-to-use are provided, which would be helpful given the many sibling tools.

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