sd_create_graph_output

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

Annotations are all false (readOnly, idempotent, destructive), so the description carries the burden. It only says 'Create', which implies mutation, but omits any additional behavioral traits such as side effects, validation, or required graph state.

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 very short (11 words) and front-loaded, but it sacrifices substance. It is concise but not informative enough; every word is used but adds minimal value.

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 the tool's complexity (7 parameters, nested objects, no schema descriptions, output schema exists but unhelpful), the description is severely incomplete. It fails to explain what an Output node is, what 'official usage metadata' means, or how to properly invoke the tool. Sibling tools add pressure for better context.

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 2-word description adds no parameter explanations. It hints at 'usage metadata' for the usages parameter but leaves 6 other parameters (graph, identifier, label, position, etc.) entirely undocumented. The description fails to compensate for the schema's lack of parameter descriptions.

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 'Create' and the resource 'Output node', and specifies 'explicit official usage metadata', distinguishing it from generic node creation tools like sd_create_node. It is specific and unambiguous.

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. alternatives (e.g., sd_create_node). No context about prerequisites, when not to use it, or recommended workflow is given.

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