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

With readOnlyHint=false and destructiveHint=false already declared, the annotations cover the safety profile, but the description adds real value by stating no other effects occur and no notification is sent. It also notes the `say` field holds a ready-to-read summary, partially compensating for the absent output schema. It stops short of describing reversibility (idempotentHint is false) or how the saved job appears afterward.

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 short sentences with the core action front-loaded and no filler. The `say` note is slightly cryptic but earns its place by pointing at the user-facing summary.

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 two-param mutation tool with no output schema, the description conveys the key facts: what is created, what is not (no sends, no other side effects), and where the readable result lives. The remaining gap is guidance on picking between the two optional parameters, which the schema already partly covers.

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 both params are documented inline ('From search_jobs or best_matches' and 'A Job Spotter post'), so the baseline of 3 applies. The description adds nothing beyond the schema about parameter selection.

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 ('a job to the person's board'), so the action is unambiguous. It does not, however, contrast itself with any sibling such as apply or log_outside_application, which is the main thing left to the agent to infer.

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?

'A bookmark: saves nothing else and sends nothing' clarifies side effects but says nothing about when to choose this over siblings like apply or log_outside_application. There is also no condition defining when to use job_id versus post_id; that is left entirely to the schema text.

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