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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description doesn't need to restate the destructive nature. It adds useful context about scope ('API key owner's personal saved-jobs pipeline') and the concept of unhearting, which supplements the structured annotations without contradicting them.

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 a single sentence that front-loads the action, specifies the scope, and provides common synonyms. No wasted words; the prefix 'Jobs —' is minimal and does not detract from clarity.

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 simple one-parameter tool with a full schema, output schema present, and annotations covering destruction/read-only flags, the description fully covers necessary context. It even clarifies ownership and pipeline semantics, leaving no important gaps for correct invocation.

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 description coverage is 100%, so the job_id parameter is fully documented in the schema. The description does not add extra semantic detail about the parameter format or constraints, which is acceptable per baseline since the schema carries the full burden.

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?

Description states a clear verb ('Remove') and resource ('a job from the pipeline'), with clarifying aliases 'unheart / remove from Saved'. It distinguishes itself from siblings like delete_resume and track_applied_job by specifying it targets the user's saved-jobs pipeline, not a resume or application tracking record.

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 clearly implies when to use: when removing a saved job from the personal pipeline. It does not explicitly name alternatives or exclusion conditions, but the context is unambiguous enough for an agent to decide without confusion against siblings such as apply_for_job or track_applied_job.

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