manage_flow_designer

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

No annotations are provided, so the description should fully disclose behavior. It mentions writes need browser auth, but the actual supported actions are only reads according to the schema. This contradiction hides the tool's true capabilities and limitations.

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 short but contains misleading information and is not structured well. It mixes general capabilities with specific action details that conflict with the schema. It could be more concise and accurate.

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?

With 25 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain most parameters, lacks return value details, and does not resolve the contradiction between described write actions and schema read-only actions.

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 52%. The description adds some context for parameters like action, confirm, and flow_id, but it's inconsistent with the schema (e.g., lists publish action not in enum). Many parameters remain unexplained.

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 claims the tool does 'read/edit' and mentions publish with confirm, but the action enum in the schema only includes read actions (list, get_detail, etc.), not write actions like publish. This contradiction makes the purpose unclear and misleading.

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?

No guidance on when to use this tool versus alternatives. The description suggests using action='publish' which is not in the schema, providing incorrect usage instructions. No comparison with sibling tools.

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