Instaffo: save a job

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

The description discloses that the operation is reversible and hints at a preview mechanism via the confirm parameter. It does not contradict the annotation (openWorldHint). No mention of authentication requirements or error states, but the core behavior is transparent.

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?

Two sentences, front-loaded with the main action, no unnecessary words. Highly efficient.

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 bookmarking tool, the description covers the main behavior, reversibility, and preview. It does not mention error cases or output schema details (though output schema exists), but is adequate given the tool's simplicity.

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%, so baseline is 3. The description adds value by noting the source of job_uuid (from instaffo_list_job_suggestions) and confirming the preview behavior of confirm, improving semantic clarity.

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 the verb (bookmark/favorite) and resource (job suggestion), and distinguishes it from sibling instaffo_unsave_job by mentioning reversibility.

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 explicitly mentions the reverse operation, guiding when to use this vs instaffo_unsave_job. It does not mention prerequisites (e.g., login status) or alternatives beyond the reversal, but the context is clear.

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