pay_agent

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

With no annotations, description carries full burden. It states 'constructs and executes' but does not disclose behavioral traits like irreversibility, fees, balance impact, or approval requirements. This lack of critical safety information limits transparency.

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 sentences, 25 words. Action verb and purpose front-loaded. Every sentence earns its place with no redundancy or fluff.

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 payment tool: explains purpose and use cases. Lacks output information (no output schema) and behavioral details, and does not differentiate from transfer_token explicitly. Given 5 parameters and many siblings, more context would be helpful.

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 100%, so parameters are well-documented. Description adds value by clarifying 'human-readable units' for amount. Baseline is 3; no significant extra semantic depth beyond schema.

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 clearly states the tool constructs and executes a direct payment to another agent, with specific use cases (services, data, compute). This distinguishes it from sibling tools like transfer_token for non-agent transfers.

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?

Description explicitly says 'Use this to pay for services, data, or compute provided by another AI agent,' providing clear context. However, it does not mention when not to use or name alternative tools for general transfers.

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