auto_apply

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

The description discloses use of browser automation (Playwright) and logging to Notion, and mentions the dry_run parameter skips submission. However, it lacks disclosure of potential side effects like state changes from applications, time consumption, rate limits, or authorization needs. With no annotations, the description carries the full burden but is only partly transparent.

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 two sentences that front-load purpose and key behaviors. It is concise without being terse, though it could be more structured (e.g., listing steps). Every sentence adds value.

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 description does not explain what the tool returns (no output schema), nor does it specify the job source (assumes remote jobs from some search). For a complex tool with 6 parameters, this is a notable gap. It partially compensates by mentioning Notion logging.

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%, but the description adds valuable context beyond schema: it explains that candidate_profile should come from parse_cv, dry_run skips submission, and min_fit_score/max_applications govern behavior. This enhances parameter understanding.

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 specific verbs ('Automatically search, score, generate cover letters, and apply') and a clear resource ('N remote jobs matching the candidate profile'). It clearly distinguishes itself from sibling tools like search_jobs, score_job_fit, and generate_cover_letter by being a composite end-to-end pipeline.

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?

While the description implies this tool is for full automation, it does not explicitly state when to use it versus using the individual sibling tools (e.g., search_jobs, score_job_fit, indeed_apply). No when-not or alternative guidance is provided.

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