add_node

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

Lacks behavioral details beyond the action itself. No mention of side effects, prerequisites, or what happens after adding (e.g., return value). Annotations are absent, so description carries full burden but does not disclose mutation behavior.

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?

Description is relatively concise with a structured Args list. Each sentence adds value, though the Args section could be tightened.

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?

Presence of an output schema reduces need to describe return values, but the description does not mention what the tool returns or any configuration requirements. Missing context for a creation tool without annotation support.

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 has 0% description coverage; description compensates with useful details: label length constraint, node_type allowed values, summary and status optionality. Adds meaning beyond the raw schema properties.

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?

Clearly states the action (add) and resource (node to session graph). Differentiates from sibling tools like export_session, record_turn, etc., as the only tool explicitly adding 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?

No explicit guidance on when to use this tool versus alternatives. Does not mention prerequisites or contexts where manual addition is appropriate.

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