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

With no annotations, the description carries the full burden. It does disclose the key behavioral facts: zero-argument default returns the current tier and exact price, tier is bounded to 1–40, and quote_qty maps to the contract's quote() ladder walk. It says nothing about error behavior for out-of-range tiers, whether values are cached/stale, or what units the price is denominated in.

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, zero filler, with the default (no-argument) behavior front-loaded ahead of the optional overrides. Every clause carries information the agent cannot get from the bare schema.

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 two-optional-parameter read tool with no output schema, the description covers defaults, ranges, and parameter semantics adequately. What is missing is minor but real: price denomination/format and behavior on invalid input, which the schema (0% coverage) and absent output schema cannot supply.

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?

Schema coverage is 0%, so the description must supply all parameter meaning, and it largely does: tier's valid range (1 to 40), quote_qty's precise semantics (contract quote() total that walks the ladder), and the default behavior when both are omitted. The remaining ambiguity is whether passing both returns two values or one combined result; "and/or" hints at combination but doesn't define the output.

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?

"Public-sale tier pricing from PairCore" names the resource (tier pricing) and the source, and the two sentences spell out the two modes: current tier with no args, or a specific tier/quote total. A verb is only implied ("pricing"), and it doesn't explicitly contrast with siblings like genesis_status or mint_instructions, but the resource is specific enough to disambiguate.

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?

It clearly states which argument combination produces which result (no args = current tier, tier = that tier's price, quote_qty = quote() total), which is genuinely useful routing. However, it gives no guidance on when to prefer this over sibling tools such as check_eligibility or mint_instructions, and no exclusions or prerequisites (e.g., sale not started, out-of-range tier).

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