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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld). The description adds context beyond them: cost-free access, escrow on Circle Arc, venue-published provenance, and the fact that posting/bidding requires using Bid-cast with EIP-191 signatures.

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 concise sentences with the key scoping and routing information front-loaded. There is little waste; even the parenthetical details earn their place by clarifying chain, provenance, and external-action requirements.

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 simple read-only search with rich annotations, the description is largely sufficient for tool selection. However, with no output schema and an undocumented optional parameter, it leaves invocation details incomplete.

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?

The schema has one optional parameter, `capability`, with 0% description coverage, and the description does not mention it at all. With low schema coverage, the description should compensate, but it provides no meaning for this 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?

The description clearly identifies the resource and scope: open, funded jobs on SML's Bid-cast board, with escrow on Circle Arc. It does not spell out an explicit verb like 'search' or 'list', but the combined name and description make the purpose unambiguous.

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?

It states the tool is free and read-only, and explicitly routes posting or bidding to Bid-cast itself, which is a useful when-not-to-use signal. It does not explicitly say 'use this when searching for open jobs', but that is strongly implied.

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