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

With no annotations provided, the description carries the full burden. It discloses an important behavioral trait: response content depends on the user's role (poster vs bidder). This goes beyond a generic read operation, though it omits details like authentication requirements or error scenarios.

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 sentences, both essential. The first sentence is action-oriented and front-loaded; the second adds crucial role-based visibility context. No wasted words.

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 tool, the core function and key nuance (role-based visibility) are present. However, given no output schema and no parameter details, it could be slightly more complete by noting expected output or parameter requirements, but it's largely adequate.

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 description provides zero information about 'task_id' or 'access_token'. Since schema description coverage is 0%, the description fails to compensate by explaining parameter purpose, requiredness, or format. The parameter names alone are insufficient.

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?

Clearly states the action 'Read bids for a task' with a specific resource. The added visibility rule ('Posters see every bid; bidders see only theirs') distinguishes it from other bid-related sibling tools and clarifies scope.

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 its use for reading bids but provides no explicit alternatives or when-not-to-use guidance. The role-based visibility hints at contextual usage but does not state when to prefer this tool over siblings like get_negotiation_details or get_task_details.

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