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

With annotations declaring read-only, the description adds crucial non-obvious server behavior: default payload only for events/listeners (actions null), only 13 of 137 types type-checked, and guessed payloads accepted but break at runtime. This is exactly the context annotations cannot provide.

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?

Front-loaded with purpose and the call-before warning, and every clause carries operational detail. The long semicolon-separated argument explanation is dense and could be better structured, but there is no wasted text.

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?

No output schema is present, yet the description specifies the return shape for each argument mode (graph model, node type lists, one node's schema/default/link types, trigger events). That sufficiently covers what an agent needs to call 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 is 100%, but the description adds meaning beyond the parameter descriptions by explaining what each mode returns (no args: graph model and workflow; outputs='fail': error-branch nodes; actionType: payload schema, default, link routing; scenarioId: accepted trigger events). This adds substantial semantic value over the 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?

States the tool returns scenario node types and the JSON schema of their polymorphic 'payload' config, and explicitly notes the OpenAPI limitation (payload typed as opaque string). This is a specific verb+resource and differentiates it from sibling schema getters.

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 instructs 'CALL THIS BEFORE creating or configuring ANY scenario node' and explains the consequence of guessing (HTTP 200 then runtime break). It does not name a sibling alternative or a when-not condition, so it falls short of full 5-level routing.

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