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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not say whether listing requires a valid license, whether it makes network calls to remote nodes (with latency or failure implications), whether results are live or cached, or what the response looks like — and there is no output schema to fall back on.

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?

One short, front-loaded sentence with the resource first and the scope qualifiers compressed into a parenthetical. Nothing is wasted, though the terseness comes at the cost of the missing behavioral detail noted elsewhere.

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, zero-required-parameter list tool with a fully documented schema, the basics are covered. But with no annotations and no output schema, the description should at minimum state the license prerequisite and roughly what a returned node entry contains; those gaps keep it at minimum-viable.

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 single parameter (notification_message) is fully documented in the schema, so the schema carries the semantics. The description adds nothing about it, which is acceptable at 100% coverage but not a value-add; the baseline of 3 applies.

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+resource ("List BrowserGPT browser nodes") and narrows scope with "local + remote" and "for the configured license." It is clearly a discovery/read operation, cleanly distinguishable from the browser_* action siblings. It stops short of naming any sibling or explaining what a "node" is.

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 phrase "for the configured license" is an implicit prerequisite hinting that set_browsergpt_license must run first, and the local/remote scope implies it should be called before picking a runner. But there is no explicit when-to-use statement, no exclusion, and no mention of ensure_remote_runner or any alternative for discovering nodes.

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