firestarter_market_preview

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

The description goes beyond annotations by explaining the read-only nature ('signed-out visitor'), the exact output (name, tagline, curated shelf), and how to use the returned listing_id. It also discloses the nuanced economics of joining and tips on surfacing drops/tiers correctly. No contradiction with annotations.

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 lengthy but each paragraph earns its place, covering purpose, workflow, and important caveats. Slight redundancy ('Preview first' repeated) prevents a 5, but structure is clear with a logical flow.

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 no output schema, the description fully explains return content (name, tagline, curated shelf) and how to act on it (buy or join). It also covers edge cases like drops and tiered early access, making it complete for the tool's complexity.

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 the schema description already explains the 'code' parameter as a share code or vanity handle. The description reinforces this but adds no new parameter semantics beyond what the schema provides.

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's purpose: preview a community market before joining, returning visible community details. It distinguishes from siblings by mentioning 'buy via firestarter_execute' and 'join (firestarter_join_market)', and from generic firestarter_preview by specifying market context.

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 explicitly says WHEN to use ('whenever a buyer pastes a market code/link or asks what is this community'), and gives alternatives (join_market, execute) and a workflow ('Preview first'). It also provides important framing guidance about not implying discounts from joining alone.

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