ps

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

The description says 'list' (read-only), but annotations set readOnlyHint: false, implying potential side effects. This contradiction misleads the agent. No additional behavioral traits are disclosed.

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?

Three words, minimal and front-loaded. It's concise but slightly under-specified for a system command; could mention 'current' or 'all' without losing conciseness.

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?

Simple tool with no parameters and no output schema. Description is minimally sufficient, but lacks details on output format or scope (e.g., user's processes vs. all). Could be improved with subtle context.

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?

No parameters exist (0 params, baseline 4). The description adds nothing beyond the schema, but since schema coverage is 100% and no params need explaining, this is acceptable.

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 'List running processes' clearly states the action and resource. It distinguishes from siblings like 'top' (for interactive monitoring) and 'system_info' (broader info), though it could be more specific about the scope (e.g., 'all processes').

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 like 'top', 'system_info', or 'tail'. The agent has no hint about context or exclusions.

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