List Xpresso Graph Nodes

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

No annotations provided; description carries full burden. Discloses read-only nature, output format (flat list, id, port summaries), and handle resolution behavior. Does not mention performance limitations.

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?

Two sentences, no fluff. Front-loaded with main action and output. Second sentence concisely explains id usage and accepted inputs.

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?

Given no output schema, description covers purpose, output structure, id usage, and handle types. Adequate for a list tool with moderate complexity.

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 a complex union. The description adds semantic value by summarizing the two main handle types (tag handle or object handle) and clarifying fallback behavior (uses first Texpresso tag).

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 verb 'Walk... and return a flat list' and the resource 'its GvNodes', with explicit aliases (Texpresso/GvNodeMaster). This distinguishes it from sibling tools like list_graph_nodes.

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?

Provides explicit guidance on using the returned `id` to address nodes in other tools (apply_xpresso_graph, etc.), and explains handle acceptance (tag or object). Lacks explicit when-not-to-use alternatives, but context is strong.

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