add_node

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

No annotations, so description carries full burden. Discloses addition behavior, positioning constraints, and property examples. Does not cover error handling, permissions, or persistence details, leaving gaps in behavioral transparency.

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?

Efficient multi-sentence structure with front-loaded purpose. Each sentence adds value (common types, properties, positioning, next steps). Slightly verbose but well-organized and readable.

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?

Covers purpose, type discovery, property examples, positioning, and follow-up actions. Lacks output description (no output schema), but for an 'add' tool the context is sufficiently complete for typical use.

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% (baseline 3). Description adds significant semantic value: example property values per type (Mountain, Erosion2, etc.) and explicit positioning logic (X spacing, Y default). Enhances understanding beyond raw schema.

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 'Add a node to the terrain graph' with specific verb and resource. Differentiates from siblings by mentioning list_node_types for type discovery and connect_nodes for wiring, thus distinguishing its role.

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 clear context: use after list_node_types and before connect_nodes. Includes positioning tips and common type examples. Lacks explicit 'when not to use' but effectively guides typical workflow.

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