Add or Update Applicant

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

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses upsert behavior (keyed by email), the ability to link job applications, and the prerequisite that stage names must already exist. It does not mention permissions, return values, or whether existing job_applications are replaced, but the disclosed details are meaningful.

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, front-loaded with the core action, and every clause earns its place. It avoids fluff and clearly packs the upsert mechanism, job-linking ability, and stage prerequisite without redundancy.

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 the moderate complexity (4 parameters, including a nested array) and lack of an output schema, the description covers the essential behavior: creating/updating, linking to jobs, and stage validation. It leaves minor ambiguity about whether job_applications replaces or appends and what the return value is, but overall it provides sufficient context for an agent to select and invoke the tool.

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?

The schema covers 100% of parameters with detailed descriptions, including the unique-identifier role of email and the stage-name prerequisite. The description adds a helpful summary of linking semantics but mostly restates schema information, so it doesn't significantly elevate understanding beyond the schema.

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 clearly states the tool creates or updates an applicant (upsert by email), and explains it can link applicants to jobs and pipeline stages. It uses a specific verb+resource combination and distinguishes itself from siblings like save_application by focusing on the applicant entity.

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 creating a new applicant or updating an existing one via email. It implicitly contrasts with read-only sibling tools like get_applicant, though it doesn't name alternatives explicitly or provide exclusions for cases like deleting.

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