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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds useful behavioral context by enumerating the possible outcome states (pending|claimed|done|failed) and noting that a launch command creates a runId. This goes beyond the annotations and clarifies what the returned history will contain.

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, information-dense sentence with no filler. It front-loads the main purpose ('See the launch/stop/open commands queued') and then packs in the outcome details and runId. Slightly better structure could separate the outcome list, but it is concise and efficient overall.

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 read-only tool with one optional parameter and no output schema, the description covers the key return aspects: command types, statuses, and runId. It could mention the effect of the 'limit' parameter or ordering, but given the low complexity and supportive annotations, the description is largely complete enough for correct 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?

The schema has one optional 'limit' parameter with min/max bounds but no description, and the tool description does not explain its meaning or effect. With 0% schema description coverage, the description should compensate, but it remains silent on how 'limit' applies to the returned history. The parameter name is semi-obvious, but the description adds no actual semantic 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: viewing launch/stop/open commands queued for the extension and their outcomes. It specifies the resource ('command history'), the action ('see'), and key details like statuses and runId. It does not explicitly distinguish itself from sibling tools like neuron_webagent_list_runs or neuron_webagent_get_run, so it falls slightly short of full differentiation.

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 this tool is for inspecting queued extension commands and their outcomes, but it does not state when to prefer it over related tools such as neuron_webagent_list_runs or neuron_webagent_get_run. No exclusions or alternative guidance are provided, leaving usage somewhat inferable rather than explicit.

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