Resume Rewrite

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

Description adds value beyond annotations: it discloses premium tier, required resume upload, and return value components (before/after bullets, missing keywords, ATS tips). Annotations declare readOnlyHint=true, and description does not contradict; it explains what the 'read' produces without implying side effects.

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?

Four sentences, front-loaded with purpose and return value. No fluff. Could be slightly more concise, but still efficient and structured well.

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?

Given no output schema, the description fully explains return values (before/after rewrites, missing keywords, ATS tips) and prerequisites (resume uploaded). Covers all necessary context for an AI agent to invoke the tool correctly.

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 coverage is 100% with well-described parameters. The description does not add significant additional meaning beyond the schema, but the schema itself is clear. Baseline score of 3 is 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?

Description clearly states the tool's purpose: generating targeted resume bullet rewrites for a specific job using the user's uploaded resume and job description. It provides concrete examples like 'rewrite my resume for this Stripe role' and distinguishes itself from sibling tools (no other tool does resume rewriting).

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?

Explicit usage guidance: 'Use for ...' with specific examples. Also states a prerequisite: user must have a resume uploaded. However, it does not explicitly mention when not to use the tool, but the context is clear enough.

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