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

No annotations exist, so the description carries the full burden and does meaningful work: it discloses the auth requirement (wallet token), the authorization constraint (poster only), the required job state (OPEN), and the resulting effect (nobody can take the job until a bid is picked or bidding closes). It omits reversibility, cost, and any error conditions, which keeps it below a 5.

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; the actor/auth constraint and the state precondition are front-loaded before the effect. Nothing is repeated from the schema or 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 two-parameter action with no annotations or output schema, the definition covers who may call it, what state is required, and what changes as a result. It leaves the bidding mechanics (window length, what bidders see) and failure behavior unexplained, which is a modest gap rather than a blocking one.

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?

At 50% schema coverage, the `token` parameter is documented in the schema, and the description adds the meaningful constraint that `job` must reference one of your own OPEN jobs. That is real added meaning, but it never clarifies what the integer is (job id) or what happens if the job is not open or not yours.

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: 'open one of your OPEN jobs to bids,' with the actor scope ('Poster only') stated up front. It is distinguishable from bids_close, bid_pick and bid_place by implication, but no sibling is named explicitly, so it falls short of 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?

The description implies preconditions (you must be the poster, the job must be OPEN) and the complementary action ('close bidding'), but never states when to choose this rather than bids_close or bid_pick. Usage is inferable rather than explicit.

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