create_flows_flow_id_deprecate

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

No annotations exist, and the description carries no behavioral context. It does not disclose side effects, reversibility, required permissions, or what happens to the flow after deprecation. The description is purely tautological and provides no transparency.

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?

While only two words long, this is under-specification rather than concise effectiveness. It lacks any meaningful content that would help an agent understand the tool.

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, no output schema, two undocumented parameters, and a tautological description, the description is far too thin to support correct invocation or outcome expectations.

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 description mentions neither flowId nor wabaAccountId. The schema itself only lists types, so there is no semantic enrichment for either parameter.

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 'Deprecate Flow' simply restates the action implied by the tool name (create_flows_flow_id_deprecate) with no additional specificity about what deprecation entails or how it differs from siblings like delete_flows_flow_id or patch_flows_flow_id_metadata.

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 provided on when to use this tool versus alternatives. The description does not mention scenarios, prerequisites, or why one would deprecate a flow rather than delete or modify it.

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