save_job

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It doesn't state whether login is required, whether saving an already-saved job errors or is idempotent, what happens to the saved job (where it appears), or what the response contains. For a mutation action with zero annotation coverage, this is a significant gap.

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 efficient sentence with zero waste. It's front-loaded with the key verb and resource. It could arguably be marginally more helpful with a usage hint, but as measured purely on conciseness, it's appropriately minimal.

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 mutation tool with no annotations, no output schema, and a single parameter, more context is needed. It doesn't clarify whether login state is required (a common requirement given sibling authentication tools), whether repeated saves are safe, or what the user sees afterward. The simplicity of the tool partially excuses some gaps, but the lack of auth/side-effect context makes it incomplete.

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% and the single parameter 'job' is documented as 'Job ID or job URL'. The description's phrase 'Save / bookmark a LinkedIn job posting' adds the context that the parameter represents a posting to be saved, complementing the schema's format hint. With only one well-documented parameter, there's little more needed.

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 clearly states it saves/bookmarks a LinkedIn job posting, with a specific verb ('save') and resource ('job posting'). It distinguishes well from siblings like 'get_job', 'search_jobs', and 'easy_apply_job' since it's clearly the act of bookmarking/persisting a job. However, it doesn't explicitly differentiate from 'get_saved_jobs' which is the inverse operation.

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?

No guidance on when to use this tool vs alternatives is provided. There's no mention of prerequisites (e.g., needing to be logged in), no note about when not to use it, and no alternative tool references. Among siblings like 'easy_apply_job' or 'get_job', a user could benefit from knowing this is the pre-application bookmarking step.

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