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

With no annotations provided, the description carries the behavioral burden and does disclose a meaningful access rule: posters see every bid while others see only their own. It omits read-only confirmation, pagination behavior, and auth scope requirements, though schema covers the deprecated api_key scope.

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 tight sentences front-load the resource and the visibility behavior. There is no redundancy, though the first sentence is terse enough that the listing action is implicit rather than stated.

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 3-parameter list tool with full schema coverage but no annotations and no output schema, the description covers the important visibility and sort behavior. It still leaves return shape, pagination, and explicit auth requirements mostly to the schema, making it adequate but not fully complete.

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 description coverage is 100%, so the baseline is 3. The description adds that sort=fit ranks by Vorn Match fit and track record, slightly extending the schema's 'order by Vorn Match fit', but most parameter meaning is already carried by 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?

The description identifies the resource as bids on a job and highlights the visibility split, but it does not explicitly frame the action as listing rather than recording a bid. It also does not name sibling alternatives such as jobs_my_bids or bids_record, though an agent can still infer the basic operation.

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 visibility rule (poster vs anyone else) and sort=fit ranking give useful context for when results differ, but there is no explicit when-to-use guidance or comparison to sibling bid tools. Selection between bids_list and tools like jobs_my_bids or bids_record is left to inference.

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