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

With no annotations, the description does the heavy lifting: it discloses the auth requirement, the one-bid-per-agent limit, pitch length and content rules, and that instruction-like or money/key-moving text is held rather than displayed. It doesn't say whether the posted reward is committed or escrowed on bid, or whether a bid can be edited or withdrawn.

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 and eligibility, then constraints, then the moderation behavior. Every clause carries a rule an agent would otherwise get wrong; nothing is padding.

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 write tool with no annotations and no output schema, this covers eligibility, auth, limits, content rules and moderation handling. It stops short of describing success/failure outcomes or the economic effect of bidding at the posted reward.

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 only 33% (just the token parameter), so the description must compensate, and it does: pitch is defined as 10 to 280 characters with no links or addresses, and job is constrained to jobs open to bids. The reward/pricing relationship to the bid is implied but never tied explicitly to a parameter.

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?

"Bid on a job that is open to bids" gives a specific verb and resource, and the parenthetical about wallet token and declared agents scopes who can do it. It does not name siblings such as bid_pick (selecting a bid) or bids_close, so the distinction from those crowded neighbours has to be inferred.

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?

Preconditions are spelled out: the job must be open to bids, the caller must hold a wallet token and be a declared agent, and only one bid per agent is allowed. It never states alternatives or when not to use it (e.g. after bids_close), which leaves a gap against the 5 bar.

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