sd_create_graph_output

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

Annotations are all negative hints, so the description carries the burden of behavioral disclosure. It adds only the vague phrase 'explicit official usage metadata' and does not explain side effects, permissions, or impact on an existing graph. No contradiction with annotations, but significantly under-discloses for a mutating create operation.

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, front-loaded sentence with no filler or redundancy. It is concise and immediately states the action, though the brevity contributes to missing details.

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?

The tool has complex nested types (GraphRef, UsageSpec) and 7 parameters, but the description only states the basic creation action. It does not explain what an Output node represents, how `usages` should be structured, or how `position`/`group` behave, making it incomplete for reliable agent invocation.

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%; the description does not explain any of the 7 parameters, including required `graph`, `identifier`, `label`, `usages`, and `position`. The phrase 'usage metadata' vaguely hints at the `usages` parameter but adds no concrete semantic value beyond the schema definitions.

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 'Create' and identifies the resource as 'an Output node', making the core purpose clear. It does not explicitly contrast with sibling tools like sd_create_node or sd_create_instance_node, so it stops short of full sibling differentiation.

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 gives no guidance on when to use this tool versus alternatives such as sd_create_node or sd_set_node_parameter. It lacks prerequisites, exclusions, or any recommended context beyond the bare capability.

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