firestarter_discover_markets

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds context beyond annotations: 'Read-only, public — no sign-in needed', and discloses the return fields. This enriches the behavioral picture (public access, no auth) without contradicting 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?

Three sentences, no filler. The first sentence states the purpose and return content; the second gives use cases; the third names alternatives and adds the read-only/auth note. Every sentence contributes essential information.

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 simple read-only list tool with one optional parameter, the description covers what it does, what data it returns, when to use it, and related tools. Annotations handle the safety profile, so no additional behavioral details are needed.

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 only parameter (limit) has a complete description in the schema. The tool description adds no additional parameter meaning, but since the schema fully describes it, baseline 3 applies.

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 states a specific verb ('Browse') and resource ('public community markets a buyer can join'), and explicitly enumerates what is returned (name, tagline, URL/handle, join code, social proof). It distinguishes from sibling tools by naming firestarter_market_preview and firestarter_join_market as alternatives.

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 provides explicit when-to-use guidance: 'Use when a buyer asks what communities exist, wants to find one to support, or says discover community markets'. It also gives clear exclusions with named alternatives: 'To see a specific community's curated shelf use firestarter_market_preview; to join one use firestarter_join_market with its code.'

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