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

Annotations already declare destructiveHint=true and openWorldHint=true, yet the description adds real value: the job is held for admin approval, is not published to the public board, and the invite link is shown only once. Minor residual tension: idempotentHint=false alongside a required idempotency key is not explained (dedupe vs. true idempotency), leaving the agent to infer the semantics.

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?

Four short sentences, front-loaded with the DESTRUCTIVE warning, then lifecycle state, then the gating condition, then the one-time return. No filler and the highest-risk information comes first.

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 13-parameter mutation with no output schema and no per-parameter descriptions, the description accounts for only the two control fields. It says nothing about budget/rate interactions, the isPublic flag's effect versus the pending_review hold, or required fields beyond the schema's own required list.

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 0% across 13 parameters, and the description only explains confirm and idempotencyKey. The remaining 11 fields — including the jobType and budgetType enums, isPublic, and the min/maxBudgetPerMin pair — carry no semantic guidance anywhere, so the agent must guess at their meaning and interactions.

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 and resource ('Creates a job') plus the exact lifecycle state it lands in ('pending_review'), which separates it cleanly from list_jobs, list_my_jobs, and respond_to_job. An agent can tell what this does without opening the 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?

'Does nothing unless confirm=true, and then requires an idempotency key' gives concrete invocation preconditions that prevent a wasted no-op call. It does not name an alternative (e.g. an update/edit path) or say when not to use it, so it falls short of full when/when-not routing.

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