bobai_nft_drop

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

No annotations are provided, so the description must cover behavioral traits. It mentions the reward is auto-minted and requires no claim, but does not explicitly state that this tool is read-only or discuss auth or rate limits. The description mixes the reward process with tool functionality, which may cause minor confusion.

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 description is two sentences, concise and front-loaded with key information. It could be slightly more structured, but it efficiently conveys the tool's purpose without unnecessary words.

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 tool with no parameters and no output schema, the description covers the essential information: remaining supply, rarity, and steps. It is complete enough for an agent to understand what the tool returns and how it relates to the reward.

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 input schema has no parameters (0 params, 100% schema coverage), so no parameter documentation is needed. Baseline for 0 params is 4; the description does not need to add anything beyond 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?

The description clearly states the tool provides info on an on-chain reward for $BOBAI purchases, with specific verb 'earn' and resource 'NFT drop'. It distinguishes from sibling tools like bobai_price or bobai_circulating_supply by describing a unique reward mechanism.

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?

The description implies the tool is used to get live remaining supply per buy-tier, rarity, and steps to earn the NFT. While it doesn't explicitly mention when not to use it or alternatives, the context from sibling names suggests it's the appropriate tool for this specific NFT drop info.

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