firestarter_join_market

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

The description adds important behavioral context beyond the annotations: it reveals that joining moves attribution to a new community, requires confirmation if switching, and that sales attribution may be conditional ('when enabled'). These details are not in the readOnly/destructive hints and help the agent understand side effects, though it doesn't cover all edge cases like invalid code recovery.

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 four sentences that front-load the core action and effect, then provide necessary caveats and usage guidance. Each sentence adds value, including the practical tip about previewing, with no wasted words or repetition.

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 single-parameter mutation with no output schema, the description covers purpose, effect, usage triggers, a prerequisite confirmation step, and an alternative tool. This is sufficient for an agent to decide when and how 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 coverage is 100% for the single 'code' parameter, which is already described as 'The market share code the community gave you.' The description merely reiterates 'share code' without adding format, validation, or example, so it does not enhance the parameter meaning beyond the schema baseline.

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 explicitly states the tool joins a community market using a share code and explains the attribution effect. It clearly distinguishes from sibling tools like firestarter_market_preview and firestarter_leave_market by focusing on the joining action and its consequences.

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 gives explicit usage triggers ('when a user pastes a Firestarter join/market code or asks to join a community's market') and suggests an alternative (firestarter_market_preview) for pre-join exploration. It also implies when to be cautious (confirm before switching communities), providing clear context.

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