get_ps_aux_top_mem_consumers

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

No annotations provided. Description only states what it lists, not how it operates (e.g., runs 'ps aux' command), required authentication, or potential side effects. Fails to disclose SSH dependency or error behavior.

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, concise but omits critical details like parameters and behavior. It is front-loaded with purpose but insufficient for operational use. Concise at the cost of completeness.

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 complexity (SSH tool with 7 params, no schema descriptions, no annotations, output schema exists), description is severely incomplete. Does not explain what output contains, command executed, security implications, or error handling. Agent cannot reliably invoke this 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?

Schema has 7 parameters with 0% description coverage. Description provides no information about any parameter (e.g., host, user, password, etc.). Agent gets no help understanding required or optional inputs beyond schema structure.

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?

Description uses specific verb 'Lists' and resource 'top 10 mem consumers' with sort direction 'MEM desc'. This clearly distinguishes from sibling 'get_ps_aux_top_cpu_consumers' by focusing on memory consumption.

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 vs alternatives (e.g., CPU counterpart, or other SSH tools). No mention of prerequisites like SSH credentials, host reachability, or OS requirements. Agent has no context for appropriate invocation.

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