firestarter_create_drop

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

Annotations already indicate destructive=true and idempotent=false. The description adds meaningful behavioral detail: it may charge the drop wallet or seller proceeds, may create a pending request needing seller approval, and can be tier-gated for early access. This goes beyond the annotations without contradicting them.

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 verbose and contains redundant phrasing: 'first-come first-served, one per member' appears both in the first and second sentences, and the funding/approval explanation is wrapped in a very long, multi-clause sentence. While informative, it could be tightened without losing meaning.

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?

Given the tool's complexity (7 params, funding decisions, approval flows) and lack of output schema, the description covers the main operational outcomes well. It explains what happens in different scenarios, but does not mention what the API returns (e.g., drop ID or status), which would be useful for follow-up calls.

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 100% and each parameter already has a description. The tool description adds cross-parameter semantics (e.g., max_claims × discount = pot, priority_hours + min_tier = tier-gated window, expires_in_hours default) and explains how funding relates to the listing owner, giving a fuller mental model than the schema alone.

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 ('Create') and resource ('community-sponsored DROP on a market you own') and clearly differentiates from the sibling tool firestarter_set_market_tiers, which 'never discounts.' This distinguishes it from similar market-related tools without needing to open schemas.

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?

Provides usage context: it explains when a drop goes live immediately vs. waits for approval, and how funding works depending on the listing owner. It explicitly contrasts with firestarter_set_market_tiers, giving an alternative, though it does not state a crisp 'use this when...' directive for all cases.

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