sys_info

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

The description claims the tool 'Reads from local hardware', implying a non-destructive read operation, which contradicts the annotation 'destructiveHint: true'. No other behavioral traits are disclosed beyond the contradictory annotation.

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 a single sentence that efficiently conveys the tool's function and key detail (local-only). No extraneous 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?

Given no output schema and the complexity of system information, the description provides a good overview of what is returned. However, it lacks details on the return format and does not address the annotation contradiction.

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 input schema has no parameters, so schema description coverage is 100%. The description adds value by detailing the information returned (CPU, RAM, disk, etc.), which is helpful 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's purpose: 'Get detailed local system information', listing specific hardware and network details. It distinguishes from siblings by highlighting that it reads from local hardware and is not available via any remote service.

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 implicitly guides usage by stating the tool reads from local hardware, suggesting it is for local system checks. However, it does not explicitly list when not to use or provide alternatives like remote services.

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