get_system_info

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

No annotations provided, so description carries full burden. 'Comprehensive' is vague—it doesn't specify what system attributes are returned (CPU, memory, OS, processes), whether the call is expensive, idempotent, or requires specific permissions.

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 sentence is appropriately brief, though the '(Phase X.3)' suffix appears to be version metadata that doesn't help an AI agent select or invoke the tool correctly.

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?

Without an output schema, the description fails to characterize what data structure or fields are returned. Given the crowded namespace of system-information tools, it lacks the contextual hints needed to distinguish its specific domain.

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?

Zero parameters with 100% schema description coverage. Baseline score applies since no parameter explanation is needed.

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 basic verb and resource ('Get comprehensive system information'), but 'system' is ambiguous given siblings like wordpress_advanced_system_info, get_system_metrics, and get_project_info. 'Phase X.3' parenthetical adds noise without clarifying scope.

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?

Provides no guidance on when to use this versus sibling alternatives (wordpress_advanced_system_info, get_system_metrics, directus_get_server_info). No mention of prerequisites or calling frequency.

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