Call allowlisted Corpay One endpoint

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

Annotations already indicate readOnlyHint=false and openWorldHint=true. The description adds that the endpoint is validated and allowlisted, and clarifies the read-only behavior is conditional on write policy. However, it does not describe response format, error handling, or cancellation behavior.

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 extremely concise with two sentences, covering purpose and a usage condition. However, it sacrifices necessary detail about parameters.

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?

With no output schema and 0% parameter coverage, the description fails to provide essential context for a 6-parameter tool. The agent lacks guidance on how to construct requests, making the tool difficult to invoke correctly.

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 0%. The description provides no explanation of the six parameters (body, query, method, pathParams, pathTemplate, idempotencyKey). An agent cannot infer their meaning or usage from the description alone.

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 that the tool calls a validated, allowlisted endpoint. The verb 'call' and resource 'endpoint' are precise, and the tool's generic nature distinguishes it from sibling tools like corpay_list_expenses or corpay_check_connection.

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 offers limited guidance on when to use this tool versus siblings. It mentions read-only unless write policy permits, which hints at safe usage, but lacks explicit when-to-use or when-not-to-use instructions.

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