export_workflow_json

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

With no annotations, the description carries the full burden, and it does disclose the key hidden side effect: this writes to a local backup file rather than returning data in-band. However, it omits critical behavioral details such as the target path, overwrite behavior, whether it fails on existing files, and whether a backup record is registered for rollback.

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?

A single short sentence with the action and destination front-loaded and no wasted words. It is efficient, though the terseness is part of why behavioral and parameter detail are missing.

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?

With no annotations and no output schema, the description should explain the returned result and the destination of the exported file, but it only gestures at 'local backup file'. For a tool that mutates local state, the omission of path, return value, and error behavior leaves the agent under-informed.

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 single workflow_id parameter has no description, minLength-only validation, and no format hints. The description does not compensate, saying nothing about where the id comes from or what form it takes beyond the implied workflow reference.

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 (Exports) and resource (workflow JSON) plus the destination (local backup file), which is more than a restatement of the name. It does not explicitly distinguish itself from siblings like update_workflow_json, list_backups, or rollback_workflow, so it falls short of a 5.

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 offers no when-to-use guidance, no prerequisites, and never mentions the related siblings (list_backups, rollback_workflow, update_workflow_json) that an agent would have to choose between. The agent must infer the role of this tool purely from its name.

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