Get Jumbo Extra's Balance

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

The readOnlyHint=true annotation already tells the agent this is a safe non-mutating read, so the description's main contribution is the word 'live', implying a real-time fetch rather than cached data. No auth/session requirement, rate limits, or edge cases (e.g., empty balance, unenrolled customer) are disclosed.

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?

A single front-loaded sentence with no filler; every word ('live', 'loyalty points balance') carries information. 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 zero-parameter read with no output schema, the description conveys enough to select and call the tool, though it could note the returned shape (points figure, expiry) or any session prerequisite. The gaps are minor given the tool's simplicity.

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to clarify and nothing misleading in the 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?

States a specific verb and resource ('get ... loyalty points balance') and scopes it to the customer's live Jumbo Extra balance. It is distinguishable from siblings like jumbo_get_stamps or jumbo_get_deposits by the resource name, but the description does not explicitly contrast itself with those near-neighbors.

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?

There is no guidance on when to call this versus jumbo_get_stamps, jumbo_get_deposits, or jumbo_get_profile, and no prerequisites such as whether a login/session is required first (jumbo_login exists as a sibling). Usage must be inferred entirely from the name.

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