Get Sezzle Payment Session

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, fully covering the safety profile. The description's 'Read' is consistent and adds a minor qualifier ('documented'), but it discloses no additional behavioral details such as error handling or return format.

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?

The description is a single, well-structured sentence of ten words that starts with the action verb. Every word contributes to understanding the tool's core function, with no redundancy or filler.

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 simple one-parameter read tool with strong annotations and complete schema coverage, the description is sufficient. It does not explicitly state the return format, but the getter semantics and lack of output schema make this an acceptable inference given the low complexity.

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?

The schema provides 100% coverage with a clear description for session_uuid ('Sezzle session UUID.'). The description's 'by UUID' adds no extra meaning beyond reinforcing the schema's parameter purpose, so it meets the baseline but does not enhance parameter understanding.

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?

The description identifies a specific action ('Read') and resource ('documented Sezzle v2 payment session') along with the key identifier ('by UUID'). This clearly differentiates it from sibling tools that validate, audit, detect, or generate data.

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?

The description implies usage when needing to read a payment session by UUID, but it provides no explicit guidance on when to prefer this over other getter tools like get_order or get_settlement_details. No exclusions or alternatives are mentioned.

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