workflow.insert_after

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

With no annotations, the description carries full burden for behavioral disclosure. It states the operation is an 'insert' (mutation) but provides no details on side effects, validation, reversibility, permissions, or error scenarios. Critical information about what happens to the workflow structure is missing.

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?

Single sentence is concise but at the expense of completeness. Every word is used, but the description lacks structure and fails to front-load key details like parameter dependency or intended use case.

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 tool has four parameters, no output schema, no annotations, and is a mutation operation, the one-sentence description is grossly insufficient. It does not explain the workflow context, parameter relationships, or what success/failure looks like. Sibling differentiation is absent.

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 0%, yet the description adds no meaning to any of the four parameters. For example, it does not explain that 'activity' is the reference activity, 'activities' are the items to insert, or how session_id and workflow_name identify the target workflow. The agent is left guessing parameter roles.

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 clearly states the action: 'Insert activities after an activity.' The verb 'insert' and resources 'activities' and 'activity' are specific, and the positional constraint 'after' distinguishes from generic insertion. However, it does not explicitly differentiate from sibling 'workflow.insert' or clarify the scope (e.g., within a 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?

No guidance provided on when to use this tool versus alternatives like 'workflow.insert' or 'workflow.remove'. The description does not mention prerequisites (e.g., workflow must exist, activity must exist) or contextual cues. Agent must infer usage from the name alone.

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