acp_pay_session

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

Discloses side effect (background document generation) and async polling requirement. No annotations provided, so description covers main behavioral traits well, though could mention idempotency or failure modes.

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 plus one follow-up instruction. Front-loaded with purpose, every sentence earns its place. No 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?

Given no output schema, description explains success behavior (document generation) and polling instruction. Covers main flow well, but could mention error handling or response format for slight improvement.

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 has 100% coverage, but description adds valuable context: bearerToken reused, sessionId provenance, Stripe PM acquisition method, and email purpose. Goes beyond schema repetition.

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 action ('Pay for an ACP checkout session'), specific resource, and distinguishes from siblings like acp_create_session and acp_get_session. It also notes the follow-up action (polling).

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?

Specifies when to use (after acp_create_session), how to obtain Stripe PM ID, and next step (poll acp_get_session). Missing explicit when-not-to-use or alternatives, but context is clear.

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