List Bids Within A Company

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds value by explaining that the tool returns a 'paginated JSON array' with 'pagination metadata' and that it only returns 'your assigned Bids.' This context helps the agent understand the output and 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?

The description is four sentences long, with the main action in the first sentence. Each sentence adds useful information, including the output format and API endpoint. It is efficient and well-structured, though the API reference lines could be considered slightly redundant.

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?

Given no output schema, the description adequately explains the output (paginated JSON array with metadata). It covers the scope ('assigned Bids'), pagination, and required parameters. It does not mention error handling or ordering, but the schema and annotations provide sufficient context for a list tool.

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 100% with good parameter descriptions. The description adds extra value by explaining how page and per_page control pagination and by noting that company_id is required. This goes beyond the schema's basic descriptions.

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 'Return a list of your assigned Bids within a Company' using a specific verb and resource. While it distinguishes from siblings like 'show_a_bid_within_a_company' by implying listing vs. retrieval, it does not explicitly name alternative tools, so it loses a point for not fully differentiating.

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 usage guidance such as 'when you need a paginated overview, to find IDs, or to filter by query parameters.' However, it does not explicitly state when not to use this tool or mention specific sibling tools, leaving room for ambiguity.

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