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

Annotations declare readOnlyHint=false, idempotentHint=false, and destructiveHint=false, but the description adds meaningful behavioral context beyond those flags: it states the product gets a 'public checkout link', that payment is confirmed by Neuron on payment, that delivery happens automatically to the buyer's WhatsApp, and that priceMinor must be in kobo with a minimum of 50000. It doesn't state idempotency implications (e.g., whether calling twice creates two products), but for a create tool with a public-link and automatic-delivery behavior, this is strong disclosure. No contradiction with annotations.

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 description is four sentences, with the core purpose and key constraints (kobo, minimum) front-loaded, then the file-delivery prerequisite, then the automated delivery outcome. Every sentence earns its place; there is no filler or repetition of the 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?

For a 24-parameter tool with nested objects and no output schema, the description provides essential preconditions (file upload before file delivery, kobo units, minimum price, automatic WhatsApp delivery on payment). It doesn't specify return values, but no output schema exists so the agent might benefit from a hint about what is returned (e.g., product ID), and it could clarify what happens when deliveryType defaults aren't set. Still, the critical context for successful invocation is present, so this is strong but not maximal.

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%, so the schema already documents every parameter. The description adds value by explaining the kobo/minor-units rule and the minimum amount inline, plus the file-upload-first requirement, which reinforces rather than repeats the schema. It does not enumerate all 24 parameters, but with full schema coverage, the baseline of 3 is appropriate; the description's extra context is a bonus.

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 verb and resource: 'Create a digital product/service with a public checkout link.' It clearly differentiates this creation tool from sibling tools like neuron_add_product_codes (adds codes to existing products) and neuron_update_product (modifies existing products). The scope is unambiguous.

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 explicitly states when to use this tool ('Create a digital product/service with a public checkout link') and provides critical operational guidance: 'For 'file' delivery, upload the file first (neuron_upload_media) and pass its URL as deliveryFileUrl.' It also names the sibling tool neuron_upload_media as a prerequisite, giving the agent an actionable alternative/sequencing. No exclusions are needed for a create operation; the context is clear.

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