workflowy_create_single_node__WARNING__prefer_ETCH

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

No annotations are provided, so the description carries the full burden. It mentions 'creates ONE node only,' which implies a write operation, but lacks details on permissions, side effects, error handling, or response format. The warning adds some context but doesn't compensate for the missing behavioral information.

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 and front-loaded with the warning, followed by the core purpose. Every sentence earns its place, with no wasted words, making it efficient and well-structured for quick comprehension.

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 complexity (7 parameters, write operation) and lack of annotations, the description is incomplete—it misses parameter details and behavioral context. However, the presence of an output schema reduces the need to explain return values, and the warning provides some guidance, keeping it from being entirely inadequate.

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 0%, so the description must compensate for undocumented parameters. It provides no information about any of the 7 parameters (e.g., 'name', 'parent_id', 'note'), failing to add meaning beyond the schema. This leaves parameters semantically unclear.

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 ('creates ONE node only') and resource ('node'), making the purpose specific and understandable. However, it doesn't distinguish this tool from its sibling 'workflowy_etch' beyond the warning, missing explicit differentiation in functionality.

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 explicitly provides usage guidance with '⚠️ WARNING: Prefer workflowy_etch (ETCH) instead,' indicating when not to use this tool and naming the alternative. This is a clear, direct instruction for tool selection.

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