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

Annotations already declare readOnly=false, destructive=false, and openWorld=true, so the safety profile is partly covered. The description adds genuinely non-redundant behavior: the product defaults to invisible so nothing is published until visible/unlisted is set, per-call confirmation is on by default, and a Cotlet API key with app access is required. It does not describe what the response contains, but adds useful state and auth context.

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?

Strong front-loading: the create action and file-URL framing come first, followed by scope, size limit, visibility default, and confirmation/auth. Mostly tight, though the confirmation concept is split across two sentences ('you confirm each call' and 'confirm with the user before each call'), a small 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 6-parameter mutation tool with no output schema, the description covers scope, the 5 GB file limit, the invisible-by-default publish state, confirmation behavior, and the API-key prerequisite. Return values are the only omission, and there is no output schema to defer to, but an agent has enough to call it correctly.

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 description coverage is 100%, including a detailed price syntax note, so the schema carries the parameter meaning. The description's mention of title, price, description, and visibility is a restatement of the schema rather than added semantics (e.g., format or interaction between visibility and publication). Baseline 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?

States a specific verb (create) and resource (a digital product from a file URL) and explicitly delimits scope by naming what this tool does NOT create (courses, coaching, memberships, physical products). An agent can distinguish it from payhip_update_product and payhip_list_products without opening any schema.

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?

Clear context: use it for a new digital product sourced from a file URL, and explicit exclusions (courses, coaching, memberships, physical products). It also flags that confirmation is required before each call, which shapes invocation. It stops short of pointing to a sibling tool for the excluded product types, so it is not a full when/when-not/alternative map.

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