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

No annotations are supplied, so the description carries the full behavioral burden, yet it discloses nothing about what the tool does operationally — no output shape, no side effects, no token/latency expectations. The only behavioral content is commercial framing ('no prompt engineering needed', '30-day support promise'), which tells an agent nothing about invocation or results.

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 of sales copy — 'instant', 'ready-to-use', 'no prompt engineering needed', '30-day support promise' — none of which help an agent decide or invoke. The single sentence of substance ('resume match workflow') is buried and contradicts the opening claim.

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 tool with no annotations, no output schema, and heavy sibling competition, the description must establish purpose, inputs, and outputs; instead it only advertises a 'prompt kit'. Nothing an agent needs in order to call it correctly 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?

With one optional parameter and 100% schema description coverage ('Optional user query to scope the analysis'), the schema already explains the parameter. The description adds no further meaning about how the query scopes the match, so the baseline of 3 applies.

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 calls itself an 'AI-powered restaurant & brand intelligence pack' but then says it generates a 'resume match workflow' — two unrelated domains, with no clear verb describing what the tool actually returns. 'Resume match' in the name is the only real signal, and it is never explained beyond being shipped as a 'prompt kit'.

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, and no mention of the dozens of sibling resume tools (resume-coach, resume-optimizer, resume-star, resume-audit-tool, etc.) that an agent must choose between. Nothing indicates what input situation should select this tool over resume-optimizer-pro or resume-tpl-tool.

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