Retrieve A Line Item Group By Id

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds that it returns a JSON object and gives the endpoint, but does not disclose additional behavioral traits beyond what annotations cover. No contradictions found.

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 reasonably concise, front-loading the purpose and including only relevant details (required parameters, endpoint). Each sentence adds value, though it could be slightly shorter without losing clarity.

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?

The description covers the essential aspects: purpose, required parameters, and return type. However, it does not address the optional pagination parameters (page, per_page) which are listed in the schema but likely irrelevant for a single-item retrieval, causing minor ambiguity. No output schema is present, but annotations compensate.

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?

Input schema has 100% coverage with descriptions for all parameters. The description lists required parameters and the endpoint path, which reinforces their usage but does not add new meaning beyond the schema. Baseline 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 clearly states the tool retrieves a line item group by ID in a company context, specifies the resource (Bid Board records), and lists required parameters. The distinction from the sibling 'retrieve_a_line_item_group_by_id_project' is evident from the endpoint path, making the purpose specific and unambiguous.

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 explicitly says 'Use this to fetch the full details of a specific Bid Board records by its identifier' and lists the required parameters. However, it does not provide explicit guidance on when to use this tool over alternatives like the project-level variant or the line-item-level tools, relying on the endpoint context instead.

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