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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds that the tool can either add or mutate status (an upsert), which is useful, but it omits auth/permission needs, what happens on duplicate tracking, or side effects of status changes.

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 front-loaded sentence that names the resource and the two core actions with no filler. It is appropriately sized, though slightly compressed given the tool's branching behavior.

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 6-parameter mutation with branching semantics (add vs. status change), the description leaves the trigger conditions and edge behavior underspecified.

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%, and the schema itself richly documents method and status with enums and defaults. The description's mention of 'Applied or Saved list' loosely maps to status values but adds no syntax or default detail beyond the schema, so baseline 3 is appropriate.

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 states a clear verb+resource ('Add a job to the user's Applied or Saved list, or change its status') and captures the upsert nature of the tool. It does not, however, explicitly differentiate itself from close siblings like apply_for_job or list_active_applications.

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 phrase 'so they can find it later' implies the intent (tracking for later reference), but there is no explicit when-to-use guidance or contrast with apply_for_job, which is the most likely confusion point. Usage is only implied.

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