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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, giving the agent the safety profile. The description adds genuine context beyond that: the budget is held in escrow and credits are simulated, plus the synchronous job_id return. It still omits what happens on timeout, cancellation/reversibility, and permission needs.

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 short sentences with zero waste, and the key outcome (job_id) is front-loaded. Nothing to trim.

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 mutation tool with nested objects and no output schema, the description does well to name the returned job_id, but the undocumented spec/acceptance/capability shape and timeout behavior leave too much for an agent to infer.

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% with 5 parameters including two nested objects, so the description must compensate and largely does not. It gives meaning only to budget (escrow), leaving capability, spec, acceptance and timeout_s undocumented.

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 ('Post a job') and the immediate outcome ('get a job_id at once'), which cleanly separates it from siblings like accept_job or deliver_job. It does not explicitly name those alternatives, keeping it just below a 5.

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?

There is no explicit when-to-use or when-not-to guidance and no reference to sibling tools such as accept_job or get_job_status. The description only characterizes the action, leaving workflow placement to inference.

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