platform_workflows

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

With no annotations, the description carries the full burden of behavioral disclosure. It provides detailed edge sourceHandle rules and node types, which is technical behavior, but it does not mention safety aspects like destructive nature of delete, side effects of publish, or permissions. The schema covers confirm for delete, but the description itself omits such cautions.

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 dense but logically organized: purpose, actions, node types, edge rules. It front-loads the main function and packs relevant details without excessive fluff. However, it is long and could benefit from bullet points or clearer separation, so not a 5.

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 18 parameters and no output schema, the description does not explain return values or outcomes for actions like list, get, or execute. It also lacks guidance on pagination beyond schema parameters. While it covers many technical details, it misses high-level context about what each action yields, making it incomplete for an agent.

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 83%, so the schema already documents most parameters. The description repeats the sourceHandle rules that are also in the schema and lists node types that appear in the nodeType description. It adds no new parameter semantics beyond what the schema already provides, so a baseline score of 3 is appropriate.

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 resource (node-based workflows) and a comprehensive list of actions (list, get, create, update, publish, execute, create_tool, delete), distinguishing it from sibling tools like platform_projects and platform_agents. It also details node types and edge rules, making its scope unmistakable.

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 lists actions but does not explicitly state when to use this tool versus alternatives. It mentions create_tool as a way to expose workflows as ProjectTools, but lacks clear 'use this when' or 'use this instead of' guidance. With many platform_* siblings, explicit differentiation is missing.

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