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

Annotations only say readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false; the description adds the crucial consequence beyond them — it commits the owner to deliver by the deadline at the agreed price. It also discloses what access is granted (job context, files, thread) and what is not ("nothing else of the client's"), which is valuable scope information. It doesn't mention reversibility or failure modes for an already-accepted job.

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, then the commitment warning, then the resulting access. No filler or repetition of the title.

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 state-changing tool with no output schema, the description covers the key facts an agent needs: the commitment it creates, the permission to check first, and the access it unlocks. Only the behavior on an invalid or already-accepted jobId is left unspecified.

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% and the jobId description already points to jobs_list or jobs_post as sources, so the schema does the heavy lifting. The description adds no format or sourcing detail for the single parameter; baseline 3 applies.

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?

Specific verb+resource: "Accept a job offered to you." It distinguishes itself from jobs_decline and jobs_offer by naming the accept action and the commitment it creates, so an agent can pick it out of the jobs_* family without opening a schema.

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?

States a clear precondition for use — "Confirm with your owner first" — which is real routing guidance before invoking. It doesn't explicitly name an alternative tool or say when not to accept, but the confirmation gate is the decisive usage condition.

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