Approve job

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

The description discloses the state transition and revocation of review links, adding value beyond annotations (idempotentHint=true, readOnlyHint=false). It doesn't contradict any annotations.

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-load the main action and state transition, then add the prerequisite for publish_job. Every sentence is necessary and 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?

With one well-documented parameter, no output schema, and annotations covering idempotency, the description sufficiently explains behavior, side effects, and prerequisites. No gaps.

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% with a clear description for jobId. The description adds no extra parameter information beyond the schema, giving a baseline score of 3.

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 tool approves a rendered job, transitioning it from draft/awaiting_review/needs_changes to approved, and revokes review links. This specific verb and resource distinguishes it from siblings like publish_job.

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?

It explicitly says 'Required before publish_job will accept the job,' providing when to use it. It doesn't list alternatives or when not to use, but the sibling list and context make this clear.

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