monitor_render

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

With no annotations, the description fully discloses behavioral traits: best-effort nature, use of stdlib subprocess with PowerShell CIM or ps, executable basename filtering, no arbitrary command-line substring matching, handling of unavailable CPU/memory with null and _warning tags, returning status=success with warnings on failures, not throwing exceptions, and applying response cap. This is exemplary transparency.

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 dense but well-structured, with the purpose stated first, followed by implementation details, failure behavior, and scope. Every sentence provides essential information without redundancy, making it appropriately sized for a tool with no other documentation.

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 there is no output schema, the description covers return behavior extensively: success status, empty/partial results, warnings, no exceptions, and response cap. It also mentions specific warning tags and field availability. The only minor gap is the lack of a complete JSON structure example, but for a monitoring tool this is sufficiently complete.

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?

The tool has zero parameters in the schema, so the baseline is 4. The description adds meaning by describing output fields (PID, name, CPU, memory, _warning) and clarifies that PID/name are always present while CPU/memory may be null. Although this is output rather than input semantics, it compensates for the lack of an output schema and adds value.

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 the tool's function: best-effort observation of husk/mantra OS processes in the bridge process. It specifies the resource (husk/mantra processes) and the action (observe), distinguishing it from sibling tools that operate on Houdini scene data or rendering.

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 provides usage context: it is bridge-only, not in the server registry, and uses subprocess instead of hou or TCP. It implies when to use (when OS-level process monitoring is needed) but does not explicitly name alternatives or exclusions, though the context is clear.

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