system_management

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

The description mentions integration with 'FastMCP 3.2 Context for real-time progress reporting and LLM-in-the-loop diagnostics', which is useful behavioral context. Since no annotations are provided, this is valuable. However, it does not disclose destructive potential, error behavior, or side effects beyond error handling.

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 structured with sections (DESCRIPTION, RATIONALE, Args, Examples) and is relatively compact for 6 parameters. It front-loads the purpose and rationale. Minor redundancy in the RATIONALE could be trimmed, but overall well-organized.

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 tool has 6 parameters, 0% schema coverage, and no annotations, the description provides thorough parameter documentation, examples, and behavioral context (telemetry). Output schema exists (not shown) but isn't needed to explain return values per instructions. It covers the tool's scope adequately.

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 description explains parameters in the Args section, detailing purpose for each (e.g., 'action: The system operation to perform', 'host: Target hostname for port testing'). Schema coverage is 0%, so description fully compensates by listing meaning for all 6 parameters, including default values and usage context.

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 states the tool performs 'system management operations' including info, health checks, and network connectivity. It lists example actions, which clarifies the resource and verb. However, it does not explicitly distinguish from siblings like 'system_health_card' or 'autonomous_troubleshooter' that also perform health checks.

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 provides a RATIONALE explaining consolidation of multiple operations, and includes example usages. However, it does not offer explicit guidance on when to use this tool versus sibling tools that may overlap (e.g., system_health_card for health, command_execution for general commands).

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