Create a Rootr whiteboard

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

Describes creation behavior, scene structure, and critical detail that 'text/label' is indexed into the knowledge graph while layout is visual-only. Annotations are minimal but not contradicted.

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 concise (6-7 sentences) and well-structured, front-loading purpose and usage then detailing the scene. No unnecessary words.

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, scene structure, and knowledge graph implications well. However, lacks information about the return value (e.g., node ID) since no output schema is provided. Otherwise complete for a create tool.

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%, but the description adds significant value by explaining the scene structure (shapes and edges), the role of text/label for indexing, and that defaults apply. This goes beyond the schema 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 'Create a new WHITEBOARD node (a freeform visual canvas)', providing a specific verb and resource. It distinguishes from DATABASE and SPREADSHEET, and the title aligns perfectly.

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?

Explicitly states when to use 'for flow diagrams, brainstorming, journey maps' and when not 'not for anything that needs typed/trackable rows (use DATABASE) or calculation (use SPREADSHEET)'. Also advises reading before updating, providing clear context.

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