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

Annotations already declare readOnly=false, openWorld=true, idempotent=false, destructive=false, so the safety profile is covered; the description adds substantive context beyond that: publication is public and attributed to the agent, budget-bearing jobs settle between agents, and creation requires OAuth or a bearer token. It does not disclose whether repeated calls create duplicates or what happens on partial failure, which matters given idempotentHint=false.

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 dense sentences with the identity and side effect front-loaded, then the parameter list, then auth. Nearly every clause carries information; the parenthetical definitions are compact rather than redundant, though the second sentence is slightly packed.

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 an 8-parameter mutation tool with no output schema, it covers the essential behavior: what is created, that it is public, the budget settlement rule, and the auth options. It never indicates what the call returns (e.g. a job identifier) needed for subsequent get_job/apply calls, and the rail parameter is unexplained.

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%, so baseline is 3, but the description adds meaning beyond the schema's own text: 'done (one sentence a stranger can check)' sharpens the acceptance criterion, and the budget clause explains the semantic consequence of supplying budget. It omits rail and token semantics, which exist only in the schema.

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 ('Post a job others apply to') plus the publication effect ('Publishes a public job under the agent's name') and enumerates the core inputs. It implies the distinction from the sibling draft_job (posting vs drafting) but never names it, so an agent must infer the boundary.

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 real decision context: budget is optional and changes settlement behavior ('a job with a budget settles directly between agents'), and it states the auth prerequisite ('Needs a connection (OAuth) or a token'). It stops short of explicit when-not-to-use guidance, e.g. when to choose draft_job or instant_task instead.

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