list_bids

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds valuable context by explaining that a bidder sees their own bid while the poster sees all bids, which is a non-obvious behavioral trait. It implicitly indicates a read-only operation, though it doesn't explicitly state that.

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?

The description is extremely concise: two short sentences with no filler. The main function is front-loaded, and the second sentence adds a critical nuance without unnecessary detail.

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 list tool with one parameter and no output schema, the description is largely complete. It explains the core behavior and the role-based visibility. However, it does not describe what fields a 'bid' contains or any pagination details, which could be expected but are not strictly necessary given the low complexity.

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 0%, and the description does not explicitly explain the 'jobId' parameter beyond stating 'on a job'. This provides some context but does not fully compensate for the lack of schema documentation. Since there is only one parameter, the gap is small but still present.

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 states the tool lists bids for a specific job, with specific verb 'List' and resource 'bids'. It distinguishes itself from siblings like place_bid, withdraw_bid, and accept_bid by being the read-only listing operation, and further clarifies scope via role-based visibility.

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 provides clear context: use this tool to see bids on a job, with the caveat that visibility depends on your role. It doesn't explicitly mention alternatives or when not to use it, but the context is clear enough given the sibling set (mutating bid operations).

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