firestarter_join_market

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

The description goes beyond annotations by disclosing that joining REPLACES any previously supported community and moves attribution for all future orders. It also clarifies that sales attribution applies only when enabled, adding meaningful nuance beyond destructiveHint and idempotentHint.

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?

Four front-loaded sentences, each earning its place: what the action does, the key destructive effect, when to use it, and the relevant alternative. No filler or redundant restatement of the tool name.

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 one-parameter tool with an output schema and annotations, the description is complete: it explains the trigger, the effect on prior support, the attribution behavior, and the preview alternative. Nothing critical is missing for correct invocation.

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 code parameter already has a clear description. The tool description adds the alias 'Firestarter join/market code' and reinforces that the code comes from the community, but it does not significantly extend what the schema already 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?

States a specific verb ('Join') and resource ('community market using its share code'), and explains the attribution effect. It also names the sibling firestarter_market_preview, distinguishing joining from previewing before commitment.

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?

Explicitly tells the agent when to invoke: when a user pastes a Firestarter join/market code or asks to join a community market. It does not enumerate exclusions, but the trigger is concrete and the preview sibling is offered as the pre-join alternative.

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