execute_contract_to_cash_invoice

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

Provides a hint about a readback requirement before issuance, but doesn't describe side effects like consuming an approval or whether it modifies state. Doesn't clarify the destructive nature despite destructiveHint true.

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?

Though concise, the sentence is cryptic and poorly structured. It's not effective communication, sacrificing clarity for brevity.

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 complex nested schema and the need for approval and readback steps, the description is grossly incomplete. Doesn't mention the approval reference, the workflow, or expected outcomes.

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?

The description does not explain any of the three required parameters (company_ref, project_ref, request). Schema coverage is 0% and the description text adds no meaning.

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 is vague and ambiguous, not clearly stating the action. 'Consume one exact approval' is cryptic and doesn't explicitly indicate that it executes a contract-to-cash invoice. Lacks a clear verb-resource relationship.

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?

No guidance on when to use this tool versus alternatives like propose_contract_to_cash_invoice or other execution tools. No mention of preconditions or context.

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