node_list

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

Annotations already declare readOnlyHint and destructiveHint, and the description adds behavioral context about the swarm manager requirement and the return format (list of full node documents including Spec, Status, ManagerStatus), going beyond the annotations.

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 concise and well-structured: a one-sentence purpose, a contextual usage note, and separate args/returns sections. Every sentence earns its place, and key information is front-loaded.

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 list tool with one optional parameter, the description covers purpose, prerequisite, return format, filter semantics, and alternatives. Combined with annotations, it provides sufficient context for correct use.

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 input schema has 0% description coverage, so the description compensates by documenting the 'filters' parameter with the attributes it can filter on (id, name, membership, role). This adds meaningful semantics, though the exact structure of the filter object is not specified.

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 opens with 'List swarm nodes,' a specific verb and resource, and clearly distinguishes this tool from siblings by pointing to node_inspect for detailed inspection and docker://nodes for computed summaries.

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 explicitly states 'Must run against a swarm manager,' a key prerequisite, and provides guidance on when to use this tool versus alternatives: drill into one node with node_inspect or read the docker://nodes resource for a computed summary.

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