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 burden of behavioral disclosure. It only states the action 'get' without detailing traits such as read-only status, authentication needs, rate limits, or output format. This is inadequate for a tool with zero annotation coverage.

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 ('Get system info'), which is efficient but under-specified. While it avoids waste, it lacks necessary detail for clarity and completeness, making it more of an under-specification issue than optimal conciseness.

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 the complexity of system information retrieval, the description is incomplete. With no annotations, no output schema, and minimal description, it fails to provide enough context for effective use, such as what data is returned or how it differs from similar tools.

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 0 parameters with 100% schema description coverage, so no parameter information is needed. The description does not add semantics beyond the schema, but this is acceptable as the baseline for zero parameters is 4, given no compensation is required.

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 'Get system info' restates the tool name 'get_system_info' with minimal elaboration, making it tautological. It specifies the verb 'get' and resource 'system info' but lacks detail on what 'system info' entails (e.g., hardware, software, configuration) or how it differs from siblings like 'get_system_monitor', resulting in vague differentiation.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention context, prerequisites, or exclusions, and it fails to reference sibling tools like 'get_system_monitor' for comparison, leaving the agent without usage direction.

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