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

No annotations exist, so the description carries the full disclosure burden, and it discloses nothing about behavior — not whether the tool reads or evaluates a retro, what it checks against, what it returns, or any limits. The 'Includes the complete prompt, usage guide, and edge-case handling' sentence describes packaged material, not the tool's runtime 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 short sentences, but all three are promotional filler rather than front-loaded substance. No sentence tells an agent what the tool does, so brevity here reflects under-specification rather than conciseness.

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?

The tool is structurally simple (one optional parameter, no output schema), which lowers the bar, but with no annotations the description still needs to say what a 'retro check' produces and how it differs from the gen/tpl siblings, and it says none of that. The mention of 'restaurant and brand teams' is the only audience signal and does not compensate.

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 schema documents the single optional 'query' parameter at 100% coverage, so the baseline is 3. The description adds nothing about how the query scopes the retro analysis, but it is not required to when the schema is already complete.

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 never states what the tool actually does with a retro. 'Turn expertise into output' and 'produce professional results in minutes' are marketing framing, and the only concrete noun phrase ('retro check tool prompt pack') largely restates the tool name rather than defining an action or output. It gives no basis for distinguishing it from the sibling pm-retro-gen-tool or pm-retro-tpl-tool.

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 guidance at all: no prerequisites, no trigger conditions, and no mention of the sibling tools that generate or template a retro. The 'usage guide' phrase refers to pack contents, not to when an agent should call this tool.

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