api_monitor_attach_process

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

With no annotations, the description carries the full burden. It says monitoring happens 'in Rohitab's background GUI', which is minor context, but says nothing about required privileges, what happens if the PID is invalid, how timeout_seconds behaves, or whether the attachment persists until detach_all is called.

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?

A single front-loaded sentence with no filler — the action and target come first. It is efficient, though quite terse for the amount of undocumented surface it needs to cover.

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?

An output schema exists, so return values need not be described, but the definition still lacks parameter meaning, behavioral constraints, and sibling differentiation for a tool with four params and zero schema coverage.

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% for four parameters. The description only implies the target process, giving no meaning for architecture, process_name, or timeout_seconds, and no format/expectation for pid beyond 'running process'.

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 gives a specific verb ('select', 'start monitoring') and resource ('a running process'), which is clear on its own. However, it does not distinguish this tool from near-identical siblings such as api_monitor_monitor_process, api_monitor_capture_process, or api_monitor_target_processes, so an agent cannot tell which one to pick from the description alone.

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?

There is no guidance on when to use this versus the many sibling process tools, nor any prerequisites (e.g., permissions, process discovery first). The agent is left to infer usage entirely.

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