firestarter_listings

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable behavioral details beyond that: it includes drafts, distinguishes between full detail (with listing_id) vs list all (without), and clarifies that live listings have share links while sandbox/draft do not. This is useful context not present in 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?

The description is exceptionally concise and well-structured: three sentences that front-load the main purpose, then explain the parameter behavior, use case, and share-link nuance. No fluff or redundancy.

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 read-only listing tool, the description is fairly complete: it enumerates the returned fields, explains the optional parameter behavior, and covers edge cases (drafts, sandbox/draft no share link). It lacks pagination or output formatting details, but those are not essential given the simple, optional-parameter design.

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 covers the single parameter with 100% coverage, but the description adds extra meaning by explaining the two modes of behavior (pass listing_id for detail, omit for a list of all listings). This goes beyond the schema description and clarifies the conditional semantics.

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 clearly states a specific verb ('View') and resource ('your own product listings'), and differentiates from siblings like 'list', 'update_listing', and 'delist' by emphasizing the seller-side read-only scope. It also lists the returned fields, making the 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 explicitly says when to use the tool ('Use this when a seller wants to see, verify, or share what they have listed'), providing clear context. It does not explicitly mention exclusions or alternatives, but the context is sufficient given the tool's read-only nature and sibling names.

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