validate_workflow_json

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

Annotations declare readOnlyHint=true, and description confirms 'offline (no API call)'. Adds specific behavioral details about validations performed (expression syntax, webhook access, etc.) beyond annotations.

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?

Two sentences with front-loaded purpose ('Validate a workflow JSON offline') and compact list of checks. No unnecessary words, highly efficient.

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 single parameter and no output schema, description explains tool purpose and validations thoroughly. Lacks output format details but is sufficiently complete for a validation 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% and describes 'workflow' as 'The workflow JSON to validate'. Description adds context about what validations are performed but does not enhance parameter semantics significantly beyond schema.

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?

Description uses specific verb 'Validate' and resource 'workflow JSON', lists exact checks (structure, unique names, connections, etc.), and distinguishes from siblings by stating 'offline (no API call)' and 'Run before create_workflow/update_workflow'.

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 ('Run before create_workflow/update_workflow') and that it's offline. Does not state when NOT to use or name alternatives, but the context with sibling tools provides sufficient differentiation.

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