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, what it returns, whether it writes files, or any permissions. Instead it offers purchase-oriented claims ('ships as a full prompt kit,' '30-day support promise') that are irrelevant to safe invocation.

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?

At three sentences it is short, but nearly every word is sales copy ('instantly,' 'no prompt engineering needed,' '30-day support promise') that does not earn its place in a tool definition. The one potentially useful phrase, 'generate a ... workflow,' is buried behind the unrelated restaurant/intelligence framing.

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?

With no annotations, no output schema, and no real explanation of input or output, the description leaves an agent unable to call this tool correctly or predict its result. Given a single optional parameter and no structured behavioral metadata, the description needed to supply the missing context and instead supplies vendor marketing.

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 100% with a single optional 'query' parameter already documented as scoping the analysis, so the schema carries the semantics. The description adds nothing about the query (expected phrasing, scope, or effect when omitted), which matches the baseline 3 for high-coverage schemas.

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 leads with 'AI-powered restaurant & brand intelligence pack,' which has nothing to do with a resume-writing tool, and then restates the name almost verbatim as a 'resume write tool workflow.' No concrete verb+resource outcome (e.g. 'drafts or rewrites resume bullet points for a target role') is stated, so an agent cannot tell what the tool actually produces.

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 at all, despite roughly a dozen resume siblings (resume-rewrite-tool, resume-polish-tool, resume-coach, resume-optimizer, resume-check-tool, etc.) that need explicit differentiation. The marketing framing about a 'restaurant & brand intelligence pack' actively misdirects rather than guiding selection.

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