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

No annotations are provided, so the description carries the full behavioral burden. It says the pack includes a complete prompt, usage guide, and edge-case handling, but does not explain whether the tool reads or writes, what it returns, what permissions are needed, or what side effects exist.

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 short, but the first two sentences are marketing slogans ('Turn expertise into output,' 'produce professional results in minutes') rather than operational information. The only useful content is the third sentence about included prompt materials.

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 low-complexity tool with one optional parameter and no output schema, the description is still too vague to support confident selection or invocation. It does not clarify the check being performed, the output format, or the scope implied by the query parameter.

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?

The input schema has one optional query parameter with 100% description coverage, so the schema already explains that it scopes the analysis. The description adds no parameter meaning beyond that, making the baseline 3 appropriate.

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 name as a 'flow check tool prompt pack' and says it helps restaurant and brand teams, but never specifies what is being checked, what the tool outputs, or how it differs from flow-gen/flow-write/flow-audit siblings.

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?

There is no when-to-use or when-not-to-use guidance. The only targeting is a vague audience mention of 'restaurant and brand teams,' which does not help an agent choose among the many flow-* sibling tools.

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