procurement_contract_to_pay

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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=true, so the safety profile is present. The description adds one useful behavioral detail—execution routes through the platform's domain-agent dispatcher under the caller's JWT, tenant, and company scope—but it does not disclose what side effects or changes the contract-to-pay action may produce.

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 compact and front-loaded: the action is named first, followed by routing context and a terse Args list. It avoids filler and every sentence contributes to understanding, though the content could be slightly expanded without losing readability.

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?

Despite an output schema being present, the description is not enough for confident selection or invocation. It never states what contract_to_pay does, what side effects to expect, or when to prefer it over the many procurement/commerce/domain-agent sibling tools, leaving the agent to infer the intended scope and payload.

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?

With 0% schema description coverage, the Args block is the only parameter documentation and does add meaning: `message` is a free-text objective and `inputs` is an optional JSON string of structured inputs. It does not specify what structured inputs are valid, how they map to the contract_to_pay action, or what a well-formed message should contain.

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 opens with a specific verb ('Run') and identifies the resource: the procurement domain agent action `contract_to_pay`. This is not a pure tautology because it clarifies this is a domain-agent dispatcher call scoped to procurement, and it is implicitly differentiated from the sibling `commerce_contract_to_pay`. However, it does not explain what the underlying contract_to_pay action actually accomplishes.

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 phrase 'procurement domain agent action' gives an implied usage context: use this when a procurement contract-to-pay behavior is needed. Yet the description provides no explicit when/when-not guidance and names no alternatives, so an agent cannot clearly distinguish this from `dispatch_domain_agent` or other procurement/commerce sibling actions.

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