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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety bar is largely met. The description still adds genuinely useful behavior context beyond them: nothing gets published and no token/authentication is required, which affects how freely an agent can call it.

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 sentence with parenthetical examples, front-loaded with what the tool produces and ending on the two key constraints. Dense but every clause earns its place; slightly parenthesis-heavy for easy scanning.

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?

No output schema exists, yet the description compensates by enumerating the draft's fields (title, summary, done line, skills, one seat). With no required parameters, no auth, and no side effects, an agent has enough to call it correctly; only the follow-up path to posting is 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 description coverage is 100% and each of the three parameters is documented in the schema, including 'never fetched' on url. The description's examples ('my API tested', 'review this pull request', 'a second opinion') illustrate the need/url pairing but add little syntax or format meaning the schema does not already carry.

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 (draft) plus resource (job) and enumerates exactly what the draft contains: title, summary, done line, skills, one seat. 'Nothing is posted' cleanly separates it from the sibling post_job, so an agent can route correctly without opening schemas.

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?

Gives the two triggering inputs ('what you need' or 'a link to check') with concrete examples, and 'Nothing is posted' signals this is the pre-publication step versus post_job. It stops short of explicitly naming post_job as the follow-up alternative, so it is clear context rather than full when/when-not guidance.

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