mcp_get_system_info

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

No annotations are provided, so the description fully carries the burden of behavioral disclosure. It does not mention any behavioral traits such as performance impact (gathering comprehensive info may be slow), return format, or side effects. The agent cannot infer whether this is a lightweight or heavy operation.

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, efficiently front-loaded. It could be slightly more informative without becoming verbose, but it earns a high score for minimalism and clear verb-noun structure.

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 zero annotations, no output schema, and a relatively simple tool, the description should indicate what 'system information' encompasses (e.g., PHP version, server software, memory usage) and the output format (e.g., plain text, JSON). The current description is too vague for an agent to reliably use the tool.

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 zero parameters with 100% schema description coverage. Since there are no parameters, the description need not add parameter meaning. A baseline of 4 is appropriate for a no-parameter tool.

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 uses 'Get comprehensive system information', which clearly specifies the verb and resource. The adjective 'comprehensive' hints that this tool aggregates multiple system aspects, distinguishing it from sibling tools like mcp_get_version or mcp_get_health that target single pieces. However, it lacks specificity on what exactly is included.

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 on when to use this tool versus individual get_* tools (e.g., mcp_get_version, mcp_get_php_info). It does not mention that this might be a broader alternative or that specific tools should be used for targeted queries. The description provides no contextual usage advice.

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