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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false and destructiveHint=false, so the safety profile is largely covered. The description still adds useful context beyond them: it performs an outbound fetch of the advert, persists it to the board, and returns a human-readable summary in `say` (valuable given no output schema). It does not warn that re-importing the same link may create a duplicate, which is the main behavioral 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?

Three short sentences, front-loaded with the action and followed by effect and output location. The first sentence is a verbatim restatement of the title, which is minor waste but the rest of the text earns its place.

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 one-parameter import tool with a full annotation set, the description covers action, side effect (saved to board, then preparable/appliable) and output location. No output schema exists, and the `say` summary reference compensates. Only idempotency/duplicate behavior is left unstated.

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 0% for the single `url` parameter, so the description must carry the load. 'Reads the advert at the link' does clarify that the URL points to a job advert rather than an arbitrary page, but adds no format constraints (http/https, supported job boards) beyond that.

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+resource ('Import a job') and elaborates with the mechanism ('reads the advert at the link and saves it to the board'), which distinguishes it from mere link-checking. It does not explicitly differentiate itself from nearby siblings like save_job or check_job_link, which are the tools an agent could most plausibly confuse it with.

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?

'from any link' implies the triggering condition (you have a job advert URL), and 'so it can be prepared and applied to' hints at the downstream workflow. However, there is no explicit when-to-use vs alternative guidance, no mention of check_job_link for validation or save_job for manual entry, and no statement of preconditions.

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