nodes_get_node

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

No annotations are provided, so the description carries the full burden. It does not disclose authentication requirements, whether the operation is read-only (implied by GET but not stated), error behavior for missing UUIDs, or what data is returned. For a read tool with zero annotation coverage, this is a significant gap.

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 text is a raw HTTP route dump plus a boilerplate tag, not a purpose-built description. It is short but under-specified rather than concise; the route and tag lines add no value an agent can act on.

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 tool with one required parameter, no annotations, no output schema, and 0% schema description coverage, the description is essentially empty of usable context. An agent cannot determine authentication needs, return shape, or error handling.

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%, and the single required parameter 'uuid' gets no explanation beyond its name. The description adds no meaning about UUID format, scope, or what the UUID identifies. With low schema coverage, the description should compensate but does not.

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 states a verb and resource ('Get node by UUID'), which is clear enough to distinguish from write siblings like nodes_update_node or nodes_delete_node. However, it restates the tool name and provides no further specificity about what a 'node' contains or how this differs from other node reads like nodes_get_nodes or system_get_nodes_metrics.

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 guidance on when to use this tool versus alternatives. The sibling list contains nodes_get_nodes (list all) and system_get_nodes_metrics, but the description never mentions when a single-node fetch is appropriate or what prerequisites exist.

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