workflow.insert

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'Insert activities before an activity' without mentioning whether the operation is destructive, reversible, or requires certain permissions. There is no information about side effects on existing activities or the workflow state.

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 a single sentence, which is concise but not informative. It essentially restates the tool name ('insert') and adds minimal context. The information-density is too low; it does not earn its place by providing useful guidance beyond the name.

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 4 parameters, no output schema, and many sibling tools that require differentiation, the description is severely incomplete. It does not explain the parameters, return values, or usage context. A user would need to infer everything from the name and schema, which is insufficient for effective tool selection.

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%, and the description adds no meaning to the four parameters ('session_id', 'activity', 'activities', 'workflow_name'). It does not explain how 'activity' and 'activities' relate, what format is expected, or the role of 'session_id' and 'workflow_name'. The description fails to compensate for the lack of schema documentation.

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 action ('insert activities before an activity') and specifies the direction ('before'), which distinguishes it from the sibling 'workflow.insert_after'. However, it does not explicitly name the alternative tool, which would improve clarity.

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 provides no guidance on when to use this tool versus alternatives like 'workflow.insert_after', 'workflow.remove', or other workflow tools. No context about prerequisites or typical use cases is given.

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