List Commitment Contract Line Items

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

Beyond annotations (readOnlyHint, etc.), the description adds that the tool returns a paginated JSON array and explains pagination controls (page, per_page) and pagination metadata. No contradictions 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?

Description is three sentences plus endpoint info, all front-loaded with key information. Every sentence adds value without redundancy.

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 covers purpose, usage, pagination, required parameters, and API endpoint. Lacks details on error handling or response structure, but the openWorldHint and simplicity of the tool (5 params, no nested objects) make it adequate.

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%. The description does not repeat schema descriptions but adds context that page/per_page control pagination and lists required parameters. This provides marginal value beyond the schema, meeting the baseline.

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?

Description clearly states the tool lists all line items for a given commitment contract, specifying the resource and action. It distinguishes from sibling tools by focusing on a specific resource (line items) and providing use cases like paginated overview and ID finding.

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?

Explicitly mentions when to use: for enumerating commitments, paginated overview, finding IDs, or filtering by query parameters. Lists required parameters. Does not explicitly state when not to use or alternatives, but the specificity of the resource makes it clear.

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