Prepare expense coding

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

Discloses key behavior: dry-run, no call to Corpay One until committed, returns operationHash. Annotations indicate readOnlyHint=true, which aligns with no side-effects until commit. No contradictions.

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?

Two effective sentences front-loading purpose and behavior. No fluff; every word adds value.

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?

Adequate for a simple tool with no output schema, but parameter explanations are missing. Workflow is clear, but parameter semantics are incomplete.

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 coverage is 0%. Description mentions categories and labels, suggesting body content, but does not explain expenseId or reason. Lacks explicit mapping to parameters.

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?

Clearly states the tool is a dry-run update for expense coding (GL account and labels), returns an operationHash, and does not commit until later. Differentiates from sibling corpay_commit_prepared_operation.

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?

Implies usage: prepare then commit. Lacks explicit when-not-to-use or alternatives, but the dry-run nature and hash return clearly guide the workflow.

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