system_management

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

No annotations are provided, so the description alone must disclose behavioral traits. It describes the tool as consolidating operations but does not mention side effects, destructive potential, or safety characteristics. The listed actions appear to be read-only, but this is not stated. More transparency is needed.

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 main description is only two sentences, clearly stating the tool's consolidated nature and how to use it. It is front-loaded and efficient. The term 'portmanteau' is concise though possibly jargon. Overall, no extraneous content.

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 a multi-action tool, with an output schema and 100% parameter coverage, the description provides sufficient context. It highlights the action parameter and vm_name requirements. However, it could better explain the rationale for consolidation or when to use specific actions. Still, completeness is high.

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?

Schema coverage is 100%, so the baseline is 3. The description adds a summary about the action parameter and vm_name requirement, but this does not significantly exceed what the schema already explains. The tool description itself does not elaborate on individual parameters 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 clearly states it is a 'comprehensive system management portmanteau tool' that consolidates system information and diagnostics. The list of actions via the 'action' parameter makes the purpose specific. It distinguishes from sibling tools like 'vm_management' which focus on VM operations.

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 advises to use the 'action' parameter and notes that most actions don't require vm_name. However, it does not explicitly provide when-to-use or when-not-to-use guidance compared to sibling tools like 'info_tools'. The schema's action descriptions give per-action requirements, but no broader alternative comparison.

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