firestarter_create_drop

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

Discloses funding mechanics, approval workflows, first-come-first-served, one-per-member, and test/live environment behavior. This goes well beyond the readOnlyHint and destructiveHint annotations, which only indicate a non-read-only, non-destructive operation.

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?

Although lengthy, every sentence adds necessary value, and the main purpose is front-loaded. No redundant phrases; the complexity justifies the length.

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?

Covers use case, funding sources, approval paths, environment behavior, and explicitly differentiates from sibling tools. With no output schema, the description does not need to explain return values, but it fully equips an agent to invoke the tool 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?

Schema already covers all 7 parameters with good descriptions (100% coverage). The description adds relational meaning such as 'max_claims × discount' for the pot and the interaction between min_tier and priority_hours, but doesn't redefine each parameter.

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 creates a community-sponsored DROP, defining it as a per-claim discount on one listing for the first N members. It explicitly distinguishes itself from tiered access (firestarter_set_market_tiers), which never discounts.

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 concrete when-to-use context with ownership scenarios (your own listing vs another seller's), immediate vs pending approval. Explicitly names alternatives like firestarter_set_market_tiers and firestarter_drop_requests, making the choice clear.

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