sd_list_graph_nodes

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds 'bounded page', which communicates pagination behavior beyond the annotations. However, it does not describe other behavioral traits such as default ordering or whether the graph must be open.

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 concise sentence that immediately conveys the core action and resource. Every word contributes value; no filler or redundancy.

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?

Despite having an output schema, the tool requires a GraphRef with package_url and graph_identifier, and has parameters like detail and offset. The description does not explain how to construct the graph reference or what detail levels mean. For a tool with a nested input object and zero schema descriptions, this is too minimal.

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%, so the description must compensate. It mentions 'bounded page' which hints at limit/offset, but does not explain the meaning of 'detail', the structure of 'graph', or how limit/offset interact. Parameters like detail (summary/full) are left entirely unexplained.

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 the specific verb 'List' with a clear resource 'nodes' and scope 'from a structured graph reference' with 'bounded page' indicating pagination. This distinguishes it from siblings like sd_get_node (single node) and sd_list_node_properties (properties of a node).

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 versus alternatives. It does not mention suitable scenarios, exclusions, or refer to sibling tools like sd_get_graph_snapshot or sd_list_node_properties. The 'bounded page' hint is the only implicit usage signal.

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