find_process

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

No annotations are provided, so the description carries full burden. It states 'This is a read-only operation with no side effects.' It also discloses that processes that exit during enumeration or require elevated access are skipped, and describes the return format (Markdown table or plain text).

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 well-structured: front-loaded with the main purpose, then usage, then return format. Every sentence adds value without redundancy. It is concise yet comprehensive.

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 no output schema, the description explains the return format in detail (Markdown table with columns or plain text for no matches). It mentions edge cases (skipped processes) and provides a complete picture for a search tool with one parameter.

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 description coverage is 0%, so description must explain the parameter. It thoroughly explains the 'name' parameter: 'Process name or substring to search for. Matching is case-insensitive and partial — "fire" matches "firefox", "Firewall", etc.' This adds significant meaning beyond the schema.

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 clearly states 'Search for running processes by name using case-insensitive partial matching.' It provides a specific verb (search), resource (running processes), and key characteristics. It also distinguishes itself from sibling tool 'get_top_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?

The description explicitly says when to use this tool vs. get_top_processes: 'Use get_top_processes instead when you want to see the highest resource consumers regardless of name.' It also explains the workflow: after finding a process, use its PID with kill_process.

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