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

Annotations declare a non-idempotent, non-destructive write; the description goes well beyond that. It discloses the auth source ('Creator dashboard -> API keys; never guess one'), that it is free, the automated screening/go-live workflow, and that flagged submissions wait for owner review. This is rich behavioral context an agent cannot derive from structured fields.

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?

Front-loaded with purpose, then auth, cost, workflow, and content rules. Every sentence earns its place, though the density of operational info makes it a touch long. Efficient and well-ordered.

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?

No output schema, so return values needn't be explained; the description covers the operational essentials (auth, cost, moderation workflow, ownership constraints). The remaining gap is field-level content guidance for the 8 required parameters, but the schema itself carries the rest.

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 low (42%) for 12 params, so the description should compensate but largely doesn't. It adds real value on api_key (format and where to obtain it) and hints at accurate claims, but says nothing about name, category, stage, pitchShort, descriptionLong, terms, tags, URLs, or price. One param enriched of twelve.

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?

States a specific verb+resource+scope: 'Submit the user's own product to the marketplace.' This implicitly contrasts with the read-only siblings (get_listing, search_listings), though it never explicitly names them. An agent can tell what it does, but sibling differentiation is left to inference.

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?

Gives clear context and constraints: requires the creator's own API key, is free, and 'Only submit real products the user owns, with accurate claims.' However, it never states when NOT to use it or points to an alternative submission flow. Clear usage conditions but no explicit exclusions.

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