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

No annotations are provided, so the description carries the full disclosure burden, and it discloses nothing behavioral: no indication of whether anything is mutated, what permissions are needed, what the tool returns, or whether the "prompt pack" is static content versus generated output. The one concrete claim, that it "Includes the complete prompt, usage guide, and edge-case handling," describes package contents rather than tool behavior.

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 sentences that never get to a functional statement: the lead sentence is a slogan, and the remaining two are sales copy. Space is spent on benefits ("in minutes", "professional results") that give an agent nothing actionable, and the actual capability is never front-loaded.

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 zero-annotation tool with no output schema, the description should at minimum say what artifact comes back (a rewritten flow document? a prompt template?). It leaves the core unknown unresolved, and the one parameter is explained only by the schema.

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?

There is a single optional parameter with 100% schema description coverage ("Optional user query to scope the analysis"), so the schema already does the work and the baseline applies. The description adds no meaning about what the query scopes or how it changes output, but it is not required to under the coverage rule.

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 restates the tool name ("flow rewrite tool") and wraps it in marketing language ("Turn expertise into output", "produce professional results in minutes") without ever saying what a "flow" is or what "rewrite" produces. With ten flow-* siblings (flow-gen, flow-polish, flow-write, flow-check, flow-summary, etc.) an agent gets no basis for telling them apart.

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 only scoping signal is an audience mention ("restaurant and brand teams"), which is a target market, not a usage condition. There is no statement of when to pick this over flow-polish-tool or flow-write-tool, and no prerequisites or exclusions.

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