List Payment Applications (Owner Invoices) For A Project

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

Annotations already declare readOnlyHint=true, so the description's claim of returning a list is consistent. The description adds pagination details but does not provide additional behavioral traits beyond what annotations offer. No contradictions.

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 about four sentences, front-loading the main action. It includes a helpful link. However, it contains some redundancy (e.g., mentions paginated array and metadata) and an unclear reference to Prime Contracts.

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 states the return type (paginated JSON array) and mentions filtering via link. However, it lacks details on default sorting, item structure, and explicit differentiation from sibling tools. This is adequate but not fully complete.

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 description coverage is 100%, so the schema documents all parameters. The description repeats that page and per_page control pagination and that project_id is required, adding minimal value 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 description clearly states it returns a list of Payment Applications (Owner Invoices) for a specified project. However, it later refers to Prime Contracts interchangeably, which may cause confusion. The distinction from similar sibling tools is not explicitly made, but the project scoping is clear.

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 gives usage context: enumerate Prime Contracts for paginated overview, find IDs, or filter. It mentions required parameter project_id and provides a link for filtering. However, it does not specify when not to use this tool or contrast it with similar tools like list_payment_applications_owner_invoices_for_prime_contract.

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