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

Goes well beyond the annotations by disclosing the PROSPECTING-only initial state, the best-effort secondary save with a warning rather than an error on failure, and that reuse can overwrite an existing application's source URL or job description (which explains the destructiveHint). Missing only auth/permission or rate-limit details.

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?

Front-loads the create-or-reuse semantics, then sequencing, then optional parameters — a logical order. Three paragraphs is slightly long, but each sentence carries operational information an agent needs.

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?

An output schema exists, yet the description still flags the two response fields an agent must act on (`alreadyExist` and the warning), and it covers ordering with update_job_application_status. Nothing an agent needs to call this correctly is missing.

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%, so the baseline is 3; the description adds real meaning by explaining that source_url and job_description are attached best-effort after create/find and may replace stored values on reuse — behavior the schema does not convey. It does not add format or length guidance for the two required string fields.

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?

States a specific verb and resource ('Creates a new job application entry in GigHQ') plus the non-obvious upsert behavior (reuses an existing active one for the same company+job). This clearly separates it from find_job_application and update_job_application among the siblings.

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?

Gives explicit routing rules: call find_job_application first if you want to inspect a possible match; call update_job_application_status with 'APPLIED' immediately after if the user has already applied. It also states an exclusion — there is no way to create directly into APPLIED/INTERVIEWING.

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