Edit Tracker workflow

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

Annotations already cover the safety profile (not read-only, idempotent, non-destructive), so the bar is lower. The description still adds real behavioral content: merge semantics for body, wholesale replacement for steps, and the fact that the response is the workflow with an incremented version.

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?

Three short sentences, front-loaded with the action, then the two facts an agent most needs before calling. No filler, though the return-value line could be seen as slightly outside the core purpose.

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?

For a mutation tool with a large nested schema, no output schema, and optimistic locking, the description covers the essentials: partial update, steps replacement, and the returned version. It omits concurrency-failure behavior and permissions requirements, which would round it out.

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%, so the baseline is 3. The description restates the merge/replace semantics already written in the body property description, and does not add format or constraint detail (e.g. what version mismatch yields) beyond 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 a specific verb and resource ('Edit a workflow') and adds the concrete mutation semantics (partial field update, steps list replacement). It does not differentiate itself from the near-name sibling tracker_workflows_update_action, which an agent could plausibly confuse with this tool.

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 when-to-use guidance, no prerequisites, and no routing versus tracker_workflows_get / tracker_workflows_create / tracker_workflows_update_action. The only indirect help is that 'version' is described as coming from workflows_get, which implies a read-then-edit flow.

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