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

Adds substantive behavior beyond the annotations: idempotency is scoped per domain, nothing is ever deleted (reinforcing destructiveHint=false), the card is a public page at sellular.online/community/<domain>, and it drives the Sellular badge link. It also discloses the auth requirement (bearer token) and the confirm-before-write step, which annotations alone do not convey.

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 the action, followed by context (public card, badge), then the idempotency and never-deletes guarantees, then prerequisites and auth. Every sentence carries information, though five sentences is on the verbose side for a one-parameter tool.

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 exists, and the description compensates by describing the resulting artifact (a public card at a predictable URL) and the per-domain idempotency semantics. It stops short of stating what the response payload contains (e.g., the card URL or a created-vs-updated flag), which is the only notable gap for a mutation tool.

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?

Single parameter with 100% schema description coverage: the schema already explains that product accepts an id, name, or domain with substring matching and is optional when the account tracks only one product. The description adds no syntax or disambiguation detail beyond that, so the baseline of 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 concrete action pair (publish a tracked product into the Sellular community directory, or refresh its existing card) on a named, well-scoped resource. It also pre-empts confusion with the misleading tool name 'list_product' by making clear this is a write/publish operation, and names the sibling (track_product) that produces the required input.

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?

Use conditions are explicit and actionable: only already-tracked products can be listed, run track_product first for anything missing, and the call requires the MCP_API_KEY bearer token plus user confirmation before writing. What is missing is guidance on when to prefer the read-side siblings (list_directory_listings, list_public_listings) or get_listing_badge instead, so alternatives are partially but not fully covered.

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