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

No annotations are supplied, so the description carries the full disclosure burden. The interrogative framing implies a read-only status lookup, but it never states what the answer looks like (paid/unpaid/pending/expired), what happens for unknown or expired session_ids, or whether the check has side effects. Adequate but noticeably thin for an unannotated tool.

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 short sentences with zero waste: the purpose comes first and the parameter instruction immediately after. Nothing is padded or restated from the title.

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?

For a one-parameter lookup with no output schema, the description covers what it answers and where the input comes from, which is most of what an agent needs. The remaining gap is the set of possible status outcomes, which would prevent misinterpretation of the result.

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% and the schema only says 'Session Id', so the description must compensate; it does by describing the parameter's origin ('the session_id that came back with the checkout_url'), which tells the agent exactly where to source the value. It still does not say whether the id is reusable, expiring, or format-constrained.

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?

Phrased as a question ('Has a checkout ... been paid?') but unmistakably a payment-status check for a checkout session, and it names the three sibling purchase tools whose sessions it inspects, which separates it from them. A direct verb form like 'Check payment status' would be crisper, but the intent and scope are clear.

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?

Establishes the workflow position explicitly: use it after buy_listing, buy_guide_spot, or buy_leads and pass the session_id that came back with the checkout_url. It does not state when not to use it or what to do if no session_id exists, but the trigger condition is unambiguous.

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