acp_get_session

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

No annotations provided, so description carries full burden. It discloses polling duration (5-30s), return values (documents, zip, credits, signup_cta), URL expiry (24h), and the required action of presenting signup_cta. This is comprehensive behavioral 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?

Single, information-dense paragraph front-loaded with purpose, then polling guidance, then return details, then key instruction. Every sentence adds value with no redundancy.

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, description fully explains return data: documents, signed_urls, expiry, zip, credits breakdown, signup_cta. Covers essential behavioral context (polling, expiry, user action needed) for correct agent invocation.

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?

Input schema has 100% description coverage on both parameters. Description adds cross-reference: 'Same bearer token used in acp_create_session' and 'session_id from acp_create_session,' clarifying tool interdependence 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?

Clearly states the tool's function: 'Get the status of an ACP checkout session.' It differentiates from sibling tools like acp_create_session (which creates) and acp_pay_session (which pays) by focusing on status retrieval and 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?

Provides explicit usage context: 'Poll after payment until status is completed' with typical timing. Also instructs to present signup_cta URL after completion. Does not explicitly state when not to use, but the polling guidance implies alternatives like waiting for completion.

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