camelot_resume_builder

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

Annotations already establish idempotency, non-destructiveness, and non-read-only behavior. The description adds meaningful behavior beyond annotations by stating 'Local browser processing,' which tells the agent that work happens client-side and implies no server upload. This contextual disclosure helps set agent expectations.

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 brief, front-loaded with the core action, and includes only useful context: what it builds, output quality, local processing, and a canonical URL. Every sentence earns its place, aside from a minor double-period typo.

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 simple resume-building tool, the description is largely complete: it states the action, input source, processing model, and export value. The existence of an output schema means return details need not be spelled out, and the annotations cover safety semantics. A small gap is the absence of any explicit guidance about export format or download behavior, but that is not critical here.

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%, so the input schema fully documents all four parameters. The description itself adds no parameter-specific meaning beyond the generic phrase 'from the details you enter,' so the 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?

The description uses a specific verb and resource: 'Create and export a structured, unwatermarked professional resume.' The phrase 'from the details you enter' clarifies input scope, and 'resume' distinguishes it from sibling document tools like camelot_cover_letter_writer and camelot_invoice_generator.

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?

The description gives clear context for when to use the tool: when a user wants a professional resume generated from entered details. It lacks explicit exclusions or named alternatives, but the resume-specific and local-processing signals make the intended use unambiguous.

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