List Line Item Types

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

Annotations indicate readOnly, which is consistent with a list operation. However, the description incorrectly states it returns Commitments, misrepresenting the behavior. It does mention pagination and filtering, adding some value, but the inaccuracy is significant.

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 moderately concise but includes redundant information (e.g., two mentions of Commitments and Line Item Types). The inclusion of a documentation link is useful. It could be more streamlined by removing the incorrect reference to Commitments.

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?

There is no output schema, so the description should explain the response structure. It mentions pagination metadata but fails to describe the fields or meaning of a line item type. The contradiction about Commitments further reduces completeness.

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 the baseline is 3. The description adds context by noting required parameters (company_id, project_id) and mentioning pagination controls (page, per_page). It also references filtering capabilities, but does not detail specific parameter usage beyond the schema.

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 first sentence clearly states the tool returns Line Item Types, but later it says 'Returns a paginated JSON array of Commitments,' creating confusion about the actual resource. The mention of Commitments contradicts the title and endpoint.

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 incorrectly suggests using this tool to enumerate Commitments, which is misleading. It does not differentiate from sibling list tools like list_commitments, and provides no clear guidance on when to use this tool versus alternatives.

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