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

Annotations declare non-readOnly, idempotent, non-destructive, and the description does not contradict them. It adds real behavioral value beyond the annotations: the 409 error code after the window closes, the ability to re-apply before close, and the underlying REST semantics (DELETE /api/v1/jobs/{job_id}/applications/me). It stops short of stating auth requirements or side effects on other state, so not a full 5.

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 'When to use' clause, then the action, precondition, and endpoint in two dense sentences with no filler. Every clause carries decision-relevant information.

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 single-parameter mutation with no output schema and full annotation coverage, the description supplies the precondition, failure mode, and reversibility needed to invoke it correctly. Only a note about authentication or authorization scope would make it fully complete.

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% for the single job_id parameter, with its own pattern and description, so the schema carries the load. The description only indirectly reinforces the parameter by embedding {job_id} in the mirrored endpoint path. Baseline 3 is appropriate when the schema fully documents the input.

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 ('Withdraw your pending application for a job') and ties it to the sibling that created the state ('you applied for a job with apply_job'). The agent can distinguish this from apply_job, claim_job, and decline_claim without opening a schema.

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?

Opens with an explicit 'When to use' trigger (applied via apply_job and no longer want it) and adds the boundary condition that the window must still be open. It also notes the failure/precondition ('409 applications_closed after') and that re-application is allowed before the close, so the agent knows both when to call and when the call will fail.

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