Get Jumbo Stamps

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read. The description adds the shape of the payload, which is useful since there is no output schema, but it says nothing about authentication (jumbo_login exists as a sibling) or any session/prerequisite behavior.

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?

One sentence, front-loaded with the verb and resource, with the payload contents following the colon. Nothing is redundant and nothing needs to be cut.

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 carries the burden of describing the return value, and it does so by listing the three categories of data returned. The main omission is whether a login/session is required, which is implied by the presence of jumbo_login among its siblings.

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 of 4 applies. The description correctly does not waste space inventing argument semantics.

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?

Names a specific verb (Read) and resource (digital stamps), then enumerates exactly what it returns: per-campaign stamp counts, active spaar campaigns, and buying-stamps balance. This partially separates it from balance-oriented siblings like jumbo_get_balance and jumbo_get_deposits by scoping the balance to stamps, though it never explicitly names those siblings.

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?

Usage is implied by the resource name: call it to inspect stamps. There is no stated condition for choosing it over jumbo_get_balance or jumbo_get_deposits, and no prerequisites, but the tool has no arguments, so the selection ambiguity is limited.

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