sezzle_get_interest_balance

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

Adds behavioral details beyond annotations: 'losslessly at four-decimal scale' indicates precision preservation, and 'Enrollment is required' warns of a prerequisite. The annotations already indicate a safe read operation, but the description adds useful context about precision and enrollment.

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, no redundant information. The core purpose is front-loaded in the first sentence, and the second sentence adds a key prerequisite. Every word earns its place.

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, the description adequately covers the purpose and a key precondition. However, it does not explain the single parameter's usage or mention potential error states, leaving minor gaps.

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 description does not mention the 'currency' parameter at all. Schema description coverage is 0%, and the description fails to compensate by explaining how the currency affects the balance. The parameter is left entirely to the schema's enum and default.

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 'Get' and clearly identifies the resource 'interest-account balance', with a precise qualifier 'losslessly at four-decimal scale'. This distinguishes it from the sibling 'sezzle_get_interest_activity', which covers activity rather than balance.

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?

No explicit guidance on when to use this tool versus alternatives. It mentions the prerequisite that enrollment is required, but does not state conditions for use or contrast with sibling tools like sezzle_get_interest_activity.

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