sysinfo

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

No annotations are provided, so the description must disclose behavioral traits. It states that CPU usage measurement requires duration >=1 and lists returned data. However, it does not explicitly state that the tool is read-only or has no side effects. The description is adequate but lacks full transparency.

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 two short sentences. The first sentence lists the outputs, the second explains the parameter. Every word earns its place; no unnecessary information.

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?

The tool lacks an output schema. The description lists the returned data (OS, CPU cores, RAM, disk space, CPU usage) but does not specify the format, units, or structure. For a simple tool, it is adequate but could be more complete.

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 schema covers 100% of the parameter (duration_sec) with a description. The tool's description adds context: 'Set duration_sec (1-20) to measure CPU usage over time,' clarifying that CPU usage measurement requires a non-zero duration. This adds meaning beyond the 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 explicitly states 'Returns system information: OS, CPU cores, RAM, disk space, CPU usage.' It uses a specific verb ('returns') and lists distinct resources, making the purpose clear. No sibling tool is similar, so no differentiation needed.

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 says 'Set duration_sec (1-20) to measure CPU usage over time,' which implies when to use the parameter. However, it does not provide when to use the tool versus alternatives, nor does it give any exclusion criteria. Usage is implied but not explicit.

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