firestarter_set_market_tiers

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

The description richly discloses behavior beyond the annotations: tiers grant access only, tiers are derived from 12-month qualifying orders, nothing is stored per member, there is no balance/expiry, and the 30-day grace period after raising a threshold. This is exactly the kind of non-obvious context agents need.

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?

Each of the four sentences carries unique, essential information and the critical purpose is front-loaded. Though longer than a two-sentence description, the complexity of tier behavior justifies the length with no filler.

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 configuration tool with no output schema, the description covers the why, when, what, and edge cases (defaults, 30-day grace, no balance/expiry, ownership requirement, relationship to market picks). It is sufficiently complete 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?

The schema already documents all parameters at 100% coverage, so the baseline is 3. The description adds value by explaining the conceptual meaning of min_orders via default examples ('Member 0 / Regular 2 / Insider 5') and clarifying that changes are derived, not stored per member.

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 opening sentence 'Configure member tiers for a community market you own' uses a specific verb and resource, and the description further scopes the exact use cases ('only call this to rename rungs, change how many orders each needs, add a 4th rung, or switch tiers off'). This clearly distinguishes it from sibling tools.

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?

Explicit usage guidance is provided: there are already working defaults, so the tool should only be called for specific modifications. It states prerequisites (owning the market) and references the related firestarter_set_market_picks tool, giving the agent a clear decision framework.

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