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

With no annotations, the description carries the behavioral burden. It discloses idempotence ('already-draft flows return success unchanged') and the side effect (flow stops processing triggers). It does not mention authentication, permissions, or whether the action affects other resources, but for the stated operation it gives sufficient 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?

The description is compact and front-loaded: purpose in the first phrase, usage examples next, and the practical pointer about flowName and idempotence after. Every sentence adds distinct value and there is no filler or repetition of schema fields.

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 two-parameter tool with no output schema and no heavy annotations, the description covers intent, identification, and behavior. The main gap is that it does not explicitly state whether at least one of flowId/flowName must be supplied, given the schema marks zero parameters as required. Still, the core information an agent needs to correctly call it is present.

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%, so the description must compensate. It explains flowName well ('its name is enough, no id lookup') and implies that flowId is an alternative identifier that is not required. However, flowId is never described in terms of format or when to use it, leaving half of the parameter surface unexplained.

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 opens with a specific verb and resource ('Unpublish (deactivate) a flow') and clearly states the effect ('stops processing triggers'). It distinguishes the tool from siblings like activate_flow and delete_flow by using 'unpublish' and 'deactivate' and by including natural-language phrasings, so an agent can confidently pick it over related 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 provides concrete user-intent examples ('pause this flow', 'stop the welcome DM', 'unpublish') and tells the agent to identify the flow by flowName without a lookup. It implies when to use this tool, but does not explicitly state when not to use it or contrast it with delete_flow or activate_flow, so it stops short of the fullest guidance.

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