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

The description only says 'update' without elaborating on effects, requirements (e.g., workflow existence), or side effects. Annotations indicate non-read-only and non-destructive, but the description adds no behavioral context beyond the verb.

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 concise sentence with no redundant information, directly stating the tool's 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?

The description omits return value details, error handling, and failure scenarios (e.g., workflow not found). While an output schema exists, the description does not clarify what happens on success or failure, leaving the tool's behavior ambiguous.

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?

Parameters are not described beyond their names. The schema has no field descriptions, and the tool description does not explain the semantics of nullable fields (e.g., whether null clears the value) or any constraints on workflow_id.

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 (update) and the specific resource (workflow's name and/or description), distinguishing it from sibling tools like update_workflow that likely handle broader changes.

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 is given on when to use this tool versus alternative update tools (e.g., update_workflow). The description lacks any mention of prerequisites, alternatives, or exclusion criteria.

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