create_node

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

There are no annotations, so the description carries the transparency burden. It discloses that a node is created and that parent_id creates a visible branch, but it does not mention persistence, generated IDs, response/return behavior, or potential side effects. This is adequate but not rich.

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?

Three short sentences: action, usage guidance, and parent linkage. The structure is front-loaded and every sentence adds value without padding.

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?

For a 6-parameter tool with no annotations and no output schema, the description plus rich input schema is sufficient to select and invoke. It covers the core creation purpose and parent-branching behavior, though it omits response/error details, which are not strictly required here.

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%, so the description need not repeat parameter meanings. It does add a small amount of context around parent_id ('so the graph shows where it branched from') and elaborates on the intent of certain types (e.g., 'decision (with reasoning)'), but this is marginal beyond the schema's existing 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 opens with a specific action and resource: 'Create a node in the task graph.' It also enumerates the node types and gives clear intent, distinguishing this creator tool from sibling operations like update_node, delete_node, and link_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?

It explicitly tells when to use the tool ('Use for every task, subtask, idea, discussion topic, note, finding... or bug') and provides conditional guidance for parent_id. It doesn't name alternative tools or exclusions, but the context is clear enough that this is the creation path versus update/link/delete.

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