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

With no annotations to fall back on, the description carries the full transparency burden and does so thoroughly. It discloses idempotency, updates to the existing card, 'nothing is ever deleted,' the bearer-token requirement, and the confirmation-before-writing behavior. These are meaningful behavioral traits beyond what the schema or name would reveal.

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 purpose is front-loaded in the first sentence, and every subsequent sentence adds essential context: card semantics, idempotency, prerequisites, and auth. It is wordier than strictly necessary—the rationale about the directory's claim could be trimmed—but it contains no filler.

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 an upsert action with no output schema, the description is complete: it explains the public URL, the update behavior, the no-deletion guarantee, the prerequisite, the auth mechanism, and the confirmation step. An agent has everything needed to decide to call it and to prepare the correct input.

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 describes the product parameter as id/name/domain with substring match and marks it optional, so the baseline is 3. The description adds value by explaining that the product must already be tracked, that the card URL is domain-based, and that the parameter can be omitted when the account tracks exactly one product.

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 opens with a specific, compound verb-resource pair: 'Put one of your tracked products in the Sellular community directory, or refresh the card it already has.' It also explains what the card is and clarifies that this is an upsert rather than a plain list, which disambiguates it from the sibling listing tools despite the slightly misleading tool name.

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 gives explicit usage boundaries: only account-tracked products can be listed, and it directs the agent to 'run track_product first for anything missing.' It also distinguishes the refresh case from the first-time creation case, giving the agent clear conditions for when this tool applies.

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