Retrieve All Line Item Groups Of A Proposal

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

Annotations already indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the safety profile is clear. The description adds that the response is a paginated JSON array and explains pagination parameters, which provides useful behavioral context beyond the annotations.

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 concise with several sentences covering the main action, pagination, required parameters, and API reference. Information is front-loaded, but it could be slightly more streamlined without the redundant 'Bid Board records' phrase.

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 the tool is a simple retrieval with full schema coverage and good annotations, the description covers pagination and required parameters. However, it lacks clarity on the exact return type (line item groups vs Bid Board records) and does not explain what a line item group is, leaving some ambiguity.

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 all five parameters described. The description lists required parameters and mentions pagination but does not add significant meaning beyond the schema descriptions. Baseline score of 3 is appropriate.

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 states 'Retrieve all line item groups of a proposal' and provides a clear verb and resource. It distinguishes from sibling tools by including 'company' in the name and mentions the specific endpoint. However, there is a slight confusion when it says 'fetch the full details of a specific Bid Board records' which seems to refer to a single record rather than all groups.

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 claims 'Use this to fetch the full details of a specific Bid Board records by its identifier,' which is inaccurate because this tool retrieves all line item groups, not a specific record. It does not provide when-to-use or exclusion guidance compared to similar tools like 'retrieve_all_line_item_groups_of_a_proposal_project'.

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