workflow_track

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

The description mentions that 'Aggregates update automatically,' which hints at side effects. It does not contradict the annotations (readOnlyHint false, etc.), but it could be more explicit about whether the operation is append-only or modifies existing records.

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 extremely concise and to the point, using a compact notation for the outcome enum. Every word adds value, and there is no redundant information.

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 simple logging tool, the description provides the essential purpose and a key side effect. However, it lacks details on parameter semantics and any caveats (e.g., whether the workflow must already exist). This leaves some gaps for an agent unfamiliar with the tool.

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?

The description explains the 'outcome' parameter partially by listing its enum values, but provides no explanation for 'workflow_id', 'notes', 'duration_ms', or 'error_details'. With 5 parameters and 0% schema description coverage, the description does not adequately clarify the meaning or usage of most parameters.

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 ('Record') and the object ('workflow execution outcome'), and enumerates the valid outcome values. It is immediately obvious what the tool does and how it differs from sibling workflow tools.

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 explains the core action but does not explicitly state when to use this tool versus alternatives like workflow_learn or workflow_predict. The context signals and sibling names imply it is for logging outcomes, but explicit guidance is absent.

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