firestarter_set_market_tiers

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

Adds significant behavioral details beyond the annotations: the 30-day no-demotion grace period, that tiers are derived from qualifying orders with no per-member storage, and that turning tiers off is possible. These are non-obvious side effects not captured by readOnlyHint or destructiveHint.

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 detailed but not wasteful; every sentence adds context about purpose, behavior, or defaults. It is well-structured, though slightly longer than necessary, but remains efficient.

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 the tool's purpose, how tiers work, defaults, the ability to add/rename rungs, and crucial behavioral nuance. Since there is no output schema, explaining return values is not required. The description is self-contained and sufficient for an agent to decide when and how to use it.

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% with descriptive parameter comments, but the tool description enriches meaning by explaining the tier system (access, not money) and the effect of raising thresholds (e.g., no immediate demotion). This goes beyond the schema's field-level descriptions.

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?

Clearly states the verb 'configure' and resource 'member tiers' for a community market, and differentiates from the sibling firestarter_set_market_picks by explaining the tier-access relationship. The description makes the tool's purpose unmistakable.

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 implies when to use the tool (to customize tier rungs, thresholds, or disable tiers) and mentions that defaults exist, so it may be optional. However, it does not explicitly contrast with alternatives despite referencing set_market_picks. Still, the context is clear enough.

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