Update Payment Application (Owner Invoice) For Prime Contract

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

Adds partial update behavior ('only the supplied fields are changed') and states mutation returns modified object. Annotations already indicate write and non-destructive. No mention of side effects, auth needs, or error handling.

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?

Front-loaded with purpose, then usage, required params, API info. Efficient but slightly redundant ('use this to update' and 'updates the specified'). Good length.

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?

Covers purpose, update behavior, required params, API endpoint. Missing explanation of nested object 'payment_application' and attachment upload requirements, though schema covers. Adequate for a tool with good schema but no output schema.

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 covers all parameters with descriptions (100% coverage). Description only mentions required params. Adds context of partial update but no additional detail per parameter beyond 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 the verb 'Update' and resource 'Payment Application (Owner Invoice) on Prime Contract', distinguishing it from create and list siblings. Minor inconsistency: says 'update an existing Prime Contracts' but actually updates the payment application.

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?

Provides guidance to use for updating existing records with partial updates ('only the supplied fields are changed'). Lists required parameters. Does not specify when not to use or alternatives like create or list.

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