discover_nodes

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

With no annotations, the description carries the full burden for behavioral disclosure. It only states 'List all' and fails to mention that results are paginated via limit/offset, that the include_gpio parameter defaults to false, or that this is a read-only operation. The meaning of 'discovered' is also unclarified.

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 redundant words. It is as concise as possible while conveying the core purpose.

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?

The tool has 6 parameters, no annotations, and no output schema, making the description insufficiently complete. It omits any mention of filtering options, pagination, the structure of returned nodes, or the meaning of 'discovered', leaving an agent without enough context to invoke the tool effectively beyond a naive list call.

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 covers 67% of parameters with descriptions, so the baseline is fair. However, the description adds no parameter semantics beyond the operation name. It does not explain the pagination behavior of limit/offset, which lack textual descriptions in the schema, but the filter parameters (role, status, cluster_id) are adequately described there.

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 action (List) and the resource (all discovered Raspberry Pi nodes). It distinguishes from siblings like get_node_info, which targets a single node, and list_clusters, which lists clusters.

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 gives no guidance on when to use this tool versus alternatives such as get_node_info for specific node details or list_clusters for cluster-level views. It also does not mention available filters or pagination, leaving the agent without decision context.

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