Register a media to sell on

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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false), so the description's main added value is the disclosure that 'Growwer reviews it in the background' — a genuine async behavior an agent needs. It does not say what the media's state is during review, what happens on rejection, or that consent flags must be true.

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?

One sentence, front-loaded with the use case, with zero redundant restatement of the title or schema.

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?

A 12-parameter creation tool with no output schema would benefit from stating what comes back (media id, pending-review status) and that the write is idempotent via requestId. The background-review note helps, but the definition remains thin for this complexity.

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 only 58% across 12 parameters, and the description only gestures at 'fees and offer' without mapping to postOffer/linkAdditionOffer or the required ownership/publishing consents. The rich nested schema descriptions carry most of the burden, leaving this at baseline.

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 and resource ('registers the media') plus what it carries (fees and offer) and that it belongs to a seller's own website. The word 'new' implicitly separates it from growwer_update_seller_media, but no sibling is named.

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 this when a seller wants to offer a new website of theirs on Growwer' gives a clear trigger condition, and 'new' implies the update/delete siblings are for other cases. No explicit when-not or prerequisite (e.g. must already be onboarded) is stated.

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