Plan Workflow

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

Annotations indicate read-only, non-destructive, idempotent behavior. The description adds significant context: the AI analyzes prompts, decides workflow count, identifies boards/columns, selects trigger/action blocks with IDs, and returns a structured plan with diagrams. No contradiction.

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 well-structured: overall purpose, agent behavior, usage guidance, parameter details, return value. It is concise with no fluff, front-loading the core purpose.

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 single parameter, good annotations, and lack of output schema, the description covers purpose, behavior, usage, and return format comprehensively. It provides enough context for an agent to use the tool 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 is 100% with a good description. The description adds extra value by specifying the maximum 2000 character limit and providing an example phrasing, enhancing the schema's explanation.

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 'plans one or more monday.com workflows' using an AI agent. It uses a specific verb (plans) and resource (workflows), and distinguishes itself from siblings like create_workflow by noting it should be used beforehand.

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 says 'Use this before create_workflow to understand how to break a complex process into individual workflows and which resources to create first.' This provides clear when-to-use and when-not-to-use guidance, and references an alternative.

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