get_system_info

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

No annotations are provided, so the description carries the full behavioral burden. It does not state whether this is a safe read-only operation (implied but not confirmed), whether it's cached, how expensive it is, or what the return shape looks like. For a zero-param diagnostic tool, the safety profile is intuitive, but the description does not confirm read-only status or latency.

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?

Single parenthetical sentence, efficiently front-loaded and low-waste. Slightly dense but appropriate for a simple tool.

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-param read operation with no output schema, the description is adequate but not rich. It does not confirm the read-only nature (though obvious), nor describe the return format or whether the output is structured. An agent can call it confidently, but some behavioral clarity is missing.

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?

With zero parameters, the baseline is 4. The description adds relevant context by listing returned fields, which compensates for the absence of parameters.

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?

States a clear verb+resource: get system information, with examples of what's returned (hostname, uptime, disk, memory, versions). Distinguishes from siblings somewhat by scope, but doesn't explicitly contrast with get_project_info or get_logs.

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?

No explicit when-to-use or when-not-to-use guidance. The agent must infer that this is for machine-level diagnostics versus project-level or log queries.

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