Save Job

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

Annotations already provide idempotentHint=true and destructiveHint=false. Description adds that saving is idempotent and explains the effect (appears on saved.html, feeds batch match scoring). No contradictions.

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?

Three sentences, each earning its place: first states main action, second explains effect, third provides usage triggers. No redundant 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 simple tool with 4 params, no output schema, and good annotations, the description covers purpose, usage, parameters, and behavioral nuance (idempotency, feed impact). 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%, baseline 3. Description adds value by noting url as convenience alternative, jobId must be passed verbatim from search_jobs, and domain is required unless url. Adds context not present in schema.

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?

Clearly states the tool saves a job to the authenticated user's saved-jobs list, with the ability to unsave. Distinguishes from sibling tools like list_saved_jobs by specifying the action (save/unsave).

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?

Provides explicit examples like 'save this one', 'bookmark these three', 'remove that from my saved jobs'. However, does not explicitly mention when not to use or alternative tools, though context signals imply listing is handled elsewhere.

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