neuron_monitor_check

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

With no annotations, the description carries the full behavioral transparency burden. It reveals that the operation forces an immediate check and can target all monitors, which is useful. However, it does not disclose side effects, return behavior, or whether monitors must be enabled; the schema partially adds the 'enabled' qualifier.

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 a single front-loaded sentence with no wasted words. It conveys the action, target, and the optional behavior efficiently.

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?

For a simple one-parameter trigger tool, the description plus schema is largely sufficient. It covers what the tool does and the all-monitors fallback. Minor gaps include lack of return/outcome details and prerequisite conditions, but these are not critical for basic invocation.

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 100%, so the monitor_id parameter is already documented. The description adds little beyond the schema—it restates the omitted-ID behavior rather than introducing new semantic detail. Baseline 3 is appropriate.

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 states the exact action—'Force an immediate check'—on a specific resource ('a monitor' or 'all monitors' if no ID is provided). It clearly differentiates this from sibling monitor tools like create, list, remove, alerts, and action by describing a distinct trigger/check behavior.

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 implies when to use the tool: when an immediate monitor check is needed, and it explains the optional monitor_id behavior. It does not explicitly name alternatives or say when not to use it, so it stops short of full guidance.

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