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

Goes beyond annotations by disclosing irreversibility, the required account-level permission, and a mandatory user-confirmation step. Since annotations already declare destructiveHint=true, the additional safety context and auth requirement are the real value here. Return/response behavior after deletion is not described.

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 destructive action and consequence, then the permission requirement and safety instruction. No filler, though the garbled product reference ("Gydmation Settings") slightly muddies the instruction.

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 single-parameter destructive tool with annotations already flagging destructiveness, the description covers what an agent must know before calling: irreversibility, permission gating, and confirmation. No output schema exists, but post-deletion response details and workflow_id sourcing are left unaddressed.

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 parameter workflow_id has no type, format, or sourcing guidance in either schema or description. It is not stated whether the value is a numeric ID, a UUID, or a name, so the description fails to compensate for the documentation gap.

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 plus resource ("Permanently delete a workflow") and implicitly distinguishes itself from non-destructive siblings like update_workflow_partial, set_workflow_active, and get_workflow. An agent can immediately tell this is the irreversible removal operation.

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?

Gives clear preconditions and a usage policy: it requires the "Allow AI assistants to delete or activate workflows" permission and instructs to confirm with the user first. It does not explicitly name an alternative (e.g. set_workflow_active for deactivation), which keeps it just short of a 5.

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