add_node

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

No annotations are present, so the description must disclose behavioral traits. It mentions the shape/style usage, but does not explain side effects such as whether the file is modified in place, how duplicates are handled, or reversibility. As a mutation tool, this lack of disclosure is a significant gap.

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 two sentences, front-loaded with the core purpose and a parameter tip. There is no filler or redundant information; every sentence earns its place.

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?

With 10 parameters and no output schema, the description is adequate but not comprehensive. The schema covers all parameters, and the description gives the essential purpose and shape/style hint, but it doesn't provide context about defaults, return values, or behavioral side effects, making it a minimally viable description.

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 100%, giving a baseline of 3. The description adds value by clarifying the relationship between the shape and style parameters (predefined shapes vs. custom style string), which goes slightly beyond the schema's individual 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 tool's function: 'Add a new node (shape/vertex) to a draw.io diagram.' It uses a specific verb and resource, and distinguishes the tool from siblings like add_edge and add_page by focusing on adding nodes (shapes/vertices).

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 clear context: this tool is for adding a single node to a diagram. It does not explicitly mention alternatives like batch_add_elements for adding multiple nodes, but the purpose is unambiguous, so it meets the 'clear context, no exclusions' bar.

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