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

No annotations, so the description carries the full burden. It usefully discloses the signing model and key handling ('hosted signing, key used for this call only and never stored'), which is real behavioral value. It says nothing about reversibility, whether funds/escrow are locked, or what happens once the owner responds.

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?

One dense sentence with the action front-loaded and the parameter sourcing right behind it; the trailing parenthetical covers the alternate signing path efficiently. Slightly overloaded with parentheticals, but no wasted prose.

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?

With 6 params, 5 required, no annotations, and no output schema, the description still explains the auth model and where the identifying params originate, which is the bulk of what an agent needs. Gaps remain around the currency param and the post-bid lifecycle, but the core is covered.

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 17% (just 'secret'), so the description must compensate, and it does for several params: owner is identified as a pubkey, slug comes from a listing, price is the bid amount, and scope is 'what you will deliver'. 'currency' is left entirely undocumented in both schema and description.

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: 'Bid on a wanted job', and it goes further by naming where the owner/slug come from (ronin_listings type wanted or ronin_me jobs). It also distinguishes itself from the sibling ronin_submit, which covers the self-signing path. An agent can pick this tool 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?

Clear context for use (bidding on a wanted-type job) and an explicit alternative for the self-sign case (ronin_submit). It omits any exclusion such as what to do for non-wanted listings or whether a pre-existing bid blocks a new one, so it stops short of full when/when-not guidance.

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