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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description goes further by disclosing the underlying mechanic (auto-mint, no claim, no signup, capped supply) and what the response contains. It does not cover refresh cadence or whether supply is chain-live vs cached, which is a minor gap for a read-only informational tool.

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 substance is front-loaded (what the reward is, how it is triggered) and closes with the routing instruction, all in two sentences. It is slightly promotional in tone ('an agent can EARN', 'no claim, no signup') but every clause carries information, so no real waste.

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 must describe what comes back, and it does: remaining supply broken out per buy-tier and rarity plus the earning steps. Combined with the usage routing and the annotations' safety profile, an agent has everything needed to call it correctly.

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 there is nothing for the description to disambiguate; the baseline for a parameterless schema applies. The description adds no spurious parameter-like instructions, which is correct.

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 names the specific resource (capped-supply collectible NFT minted per $BOBAI buy >= $100) and the specific output (live remaining supply per buy-tier and rarity, plus steps to earn). It also explicitly differentiates itself from the sibling bobai_purchase_guide, so an agent can identify its role without opening the schema.

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 states the exact trigger condition ('use it before a buy of $100 or more to see which NFT it would mint') and names the alternative tool for the actual buy ('for the buy itself use bobai_purchase_guide'). When-to-use and when-to-use-something-else are both explicit.

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