Get Sezzle Merchant Context

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds value by specifying the return payload is non-secret and covers environment, merchant, safety, and permission categories, which is beyond the annotations. It clarifies the tool returns contextual information without exposing secrets.

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 that front-loads the action ('Return') and immediately clarifies the scope. Every word contributes to understanding the tool's purpose, 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, the description is the sole source of information about return values. It lists high-level categories but does not detail the structure or meaning of 'safety' or 'permission' context. For a simple context tool, this is adequate but leaves some ambiguity.

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 input schema is empty with zero parameters, so the description does not need to explain parameter semantics. Baseline for zero parameters is 4; the description adds no parameter-specific details, but none are required.

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 uses a specific verb 'Return' and clearly identifies the resource as 'non-secret environment, merchant, safety, and permission context' for the server process. It distinguishes itself from sibling tools like sezzle_get_order or sezzle_get_settlement_details by focusing on the process context rather than a specific business record.

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 its use when general context about the server process is needed, but it does not explicitly state when to use it over alternatives or provide exclusions. No mention of sibling tools or scenarios where another tool would be more appropriate.

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