flatten_node

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

No annotations are provided, so the description carries full burden. It states the tool flattens a node into a single vector, implying a destructive merge, but does not disclose reversibility, resource effects, or required permissions. The description is too brief to ensure the agent understands the behavioral implications.

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 extremely concise, consisting of two short sentences with no wasted words. It efficiently conveys the core purpose and a typical use case.

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?

Given the tool's simplicity (one parameter, no output schema), the description is adequate but not complete. It omits important behavioral details (e.g., whether the operation is reversible, what happens to child nodes) that would help an agent use it correctly.

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 for parameters is 100% (nodeId has a schema description). The tool description does not add extra meaning beyond the schema's 'Node ID to flatten'. Baseline 3 is appropriate since the schema already documents the parameter, but the combined information is minimal.

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 action ('Flatten a node (or group) into a single vector'), which is a specific verb+resource. It distinguishes this tool from siblings like 'group_nodes' or 'convert_to_component' by using 'flatten', implying merging into a vector path. However, it could be more precise about what 'flatten' entails.

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 a use case ('cleaning up imported SVG icons'), which gives context. However, it lacks explicit guidance on when not to use this tool or alternatives, such as grouping vs flattening.

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