Deals, flash sale and campaigns

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuinely new behavioral detail: results are ordered biggest-discount-first and the payload includes flash-sale end time and shop discount codes – facts an agent cannot derive from the annotations or schema.

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 core purpose, then supporting content detail, then usage and alternatives in two tight sentences. No filler and no repetition of structured fields.

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?

An output schema exists, so return values need no explanation; the description still conveys scope, ordering, and when to prefer siblings. For a read-only single-parameter listing tool, everything needed to select and invoke it is present.

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?

Only one parameter (limit) and schema description coverage is 100%, so the schema already documents it. The description says nothing about the limit or its default of 30, which is acceptable but adds no value over the schema – the baseline 3.

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+resource ('List today's featured deals from the Shopino home page') and enumerates the content rows returned (flash sale, best sellers, newest, themed, campaigns, discount codes). It is immediately distinguishable from sh_browse, sh_search and sh_campaign by naming them.

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?

Gives an explicit trigger ('Use for "what's on sale" / "best discounts today"') and routes to alternatives with their conditions: sh_campaign(slug) to open a campaign, sh_browse(discounted_only=true, sort='biggest_discount') for every discounted product in a category.

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