Save Job

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

Annotations already declare openWorldHint=true and destructiveHint=true, but the description adds nothing beyond the title: no indication that saving is a persistent, idempotent write to the user's saved list, no note that it is reversible via unsave_job, and no auth or failure context. A one-line description for a mutating, open-world tool leaves behavior largely undisclosed.

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 short sentence with no filler, so it is maximally concise. The tradeoff is that nothing is front-loaded beyond the bare purpose, but it does not waste words.

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?

With an output schema present, return values need not be explained, and only one parameter exists, so the description covers the minimum needed to invoke the tool. It is still incomplete about mutation semantics, idempotency, and its relationship to unsave_job/get_saved_jobs.

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% and the single parameter job_url is already documented as 'Full URL of the job posting.' The description adds no format hints (e.g., canonical LinkedIn job-view URL vs. tracking URL). Baseline 3 applies when the schema already carries the parameter semantics.

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 (Save) and resource (LinkedIn job posting), which is unambiguous and matches the tool name. It does not, however, distinguish itself from close siblings like unsave_job, get_saved_jobs, or apply_to_job, so the agent must infer the routing itself.

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 gives no when-to-use guidance, no mention of prerequisites (e.g., being logged in, whether the job must exist), and no pointer to the inverse tool unsave_job or to get_saved_jobs for verification. Usage is only implied by the name.

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