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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=true. The description adds that this writes to a list and mutates status, but it never discloses the destructive aspect flagged by the annotation — e.g. whether changing status overwrites a prior stage — nor any auth or overwrite semantics, leaving a notable gap for a mutation tool.

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?

A single efficient sentence front-loads the action and outcome with no wasted text. The redundant 'Jobs —' title prefix is the only minor inefficiency.

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, so return values need not be explained, and annotations cover safety. However, for a destructive, idempotent mutation living among closely related job-application siblings, the description does not clarify its boundary versus apply_for_job or submit_application, leaving the agent to infer routing.

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 67%, so the schema documents most parameters (job_id source, method/status enums with defaults). The description mentions no parameters, and the two undocumented fields (job_title, company_name) are self-evident; adds little beyond structured data, so a baseline 3 fits.

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 specific verbs (add to list, change status) and the resource (a job in the user's Applied/Saved list), plus the outcome (so they can find it later). It does not explicitly differentiate from the many sibling job tools (apply_for_job, submit_application, steer_application), so it falls short of a 5.

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 implies when to call it (when a user applies or saves a job so it can be found later), but gives no explicit when-not guidance and never names the alternative sibling tools it could be confused with, such as apply_for_job or submit_application.

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