system_snapshot

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

No annotations are provided, so the description must carry the burden. It states what data is returned but does not disclose any behavioral traits such as performance impact, read-only nature, or potential latency. For a comprehensive snapshot, some caveats might be expected.

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, the first front-loaded with the tool's action and scope. Every word adds value; no fluff.

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 zero parameters and an output schema present, the description adequately lists the data categories. It is complete for a snapshot tool but could mention that it aggregates data from siblings.

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 and schema coverage is 100% (vacuously). Per calibration, baseline for 0 parameters is 4. The description does not need to add param details.

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 uses 'EVERYTHING in one call' and lists specific categories (inventory, live sensors, CPU/GPU/memory/disk/network), clearly identifying the tool's purpose as a comprehensive system overview. It distinguishes from siblings like cpu_status or disk_health, which are more specific.

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 phrase 'The "tell me everything about this machine" tool' implies use when a broad overview is needed. Sibling tools are listed, suggesting alternatives for specific data, but no explicit when-not-to-use or alternative names are given in the description.

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