Retrieve All Line Item Groups Of A Proposal

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

Annotations provide read-only and idempotent hints. The description adds value by detailing pagination behavior, required parameters, and the API endpoint. No contradiction with 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 no wasted words. It front-loads the purpose and includes relevant details like pagination and endpoint, though the API version info is somewhat extraneous.

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 annotations and schema, the description adequately explains the tool's behavior, pagination, and required parameters. It mentions the return type (pagination metadata) despite no output schema. Minor gap: no mention of the company-scoped alternative.

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%, so baseline is 3. The description adds minimal extra context about pagination parameters but does not significantly enhance understanding beyond the schema 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 the action 'Retrieve all line item groups of a proposal' and distinguishes from the sibling tool by specifying the project scope. The verb is specific and the resource is well-defined.

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 mentions pagination control but does not explicitly state when to use this tool versus alternatives like the company-scoped sibling. The guidance is implied but not explicit about exclusions or context.

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