procurement_contract_to_pay

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

The description discloses that the tool routes through the platform's domain-agent dispatcher with JWT, tenant, and company scope, providing some behavioral context. However, with no annotations, it fails to disclose side effects, required permissions, or limitations of the underlying action.

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 short and front-loaded with the primary purpose. It efficiently covers the routing mechanism and parameters in a few sentences, with no redundant information.

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 having an output schema, the description does not mention what the action returns or provide sufficient context about the domain action's scope. For an agent tool with 0% schema coverage and no annotations, the description omits critical details such as expected outcomes and when the action is applicable.

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 description adds meaning by labeling `message` as a free-text objective and `inputs` as optional JSON. However, it does not explain expected JSON structure, constraints, or examples, which is insufficient to compensate for the schema's lack of descriptions.

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 states it runs the procurement domain agent action `contract_to_pay`, which indicates it executes a specific action. However, it does not explain what the action does (e.g., converting contract to payment) and lacks differentiation from sibling tools like procurement_po_approval_workflow or commerce_contract_to_pay.

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?

There is no guidance on when to use this tool versus alternatives. The description does not specify contexts, prerequisites, or exclusions, leaving the agent without decision support for tool selection.

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