get-node-set-detailed-info

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

No annotations are provided, so the description must disclose behavioral traits. It says 'retrieves source code', implying read-only, but does not explicitly state side effects, auth requirements, or rate limits. The description is insufficient for a tool with no 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 brief with two sentences. The first sentence states the action, the second provides parameter examples. It is concise but could be structured more clearly by separating the purpose from the parameter listing.

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?

With no output schema, the description does not explain the return format or content beyond 'source code'. It also fails to differentiate from similar tools (e.g., get-node-detailed-info). The description is adequate for a simple tool but lacks completeness for effective selection.

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 coverage is 100% with basic descriptions. The tool description adds concrete examples for both parameters (module and set), which aids understanding beyond the schema. This adds value, justifying a score above the baseline of 3.

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 it retrieves source code for a node module, but the tool name refers to 'node-set', implying a set context. The description includes both module and set parameters, so the purpose is mostly clear but could explicitly mention 'node module set' for better specificity.

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 provides no guidance on when to use this tool vs siblings like get-node-detailed-info or find-nodes-by-type. It does not mention alternatives or exclusion criteria, leaving the agent without usage context.

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