list_unmanaged

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

With no annotations provided, the description carries full behavioral burden. The explicit [READ] marker discloses that this is a read-only operation, and the phrase 'now or with a scheduled future unmanage window' clarifies exactly which nodes are included. It does not describe output format or permissions, but for a simple read-only list this is meaningful disclosure.

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 compact and front-loaded, stating the core purpose in the first line and documenting the argument immediately after. Every sentence earns its place with no redundant wording.

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 one-parameter read-only tool with no output schema, the description covers the essential invocation details and result scope. It could be more complete by pointing to related maintenance tools or describing the returned node fields, but the current level is sufficient for basic correct usage.

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%, but the description fully explains the only parameter: target is the SolarWinds target name from config and can be omitted for the default. This adds real semantic meaning beyond the schema's bare 'Target' label.

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 uses a specific verb-resource pairing: lists nodes that are unmanaged now or scheduled for a future unmanage window. This clearly distinguishes it from related tools like list_muted and unmanage_node, so an agent can identify its purpose without ambiguity.

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?

There is no explicit guidance about when to use this tool versus alternatives such as nodes_list, list_muted, or unmanage_node. The target configuration note is a parameter detail, not a usage condition or exclusion, so the agent is left to infer when this tool is the correct choice.

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