api_monitor_target_processes

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

No annotations are provided, so the description carries the full burden. It does disclose useful behavioral context via 'current' (a live snapshot) and eligibility for attach, but it says nothing about whether API Monitor must be running, permissions, or ordering guarantees.

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 efficient sentence with the resource front-loaded after the verb. It is not padded, though it is arguably under-specified rather than compressed.

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 explained, but the two undocumented parameters and the absence of any annotation coverage leave real gaps for a discovery tool whose main job is filtering and selection.

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% and neither of the two parameters (limit, query) is mentioned in the description. The agent has no idea that results can be filtered by query or capped by limit, so the description fails to compensate for the empty 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?

States a specific verb ('List') and resource ('current Windows processes that can be selected for API Monitor attach'), which is clear and scoped. It does not, however, explicitly distinguish itself from close siblings like capture_list_processes or api_monitor_attach_process.

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 when-to-use or when-not-to-use guidance is given, and no alternative is named. The phrase 'can be selected for attach' only weakly implies this is a pre-attach discovery step, leaving the agent to infer the workflow and the difference from capture_list_processes.

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