Get product specs

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds genuine behavioral context the annotations do not: the response includes editorial pros/cons and a currency-specific price range in Toman, which sets expectations for a tool with no output 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?

Two short sentences, front-loaded with the payload contents and followed by the sequencing hint. No filler, no repetition of the title, and no redundancy with 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?

With no output schema, the description correctly compensates by enumerating the four data categories returned. Minor gaps remain around whether price range is per-variant and whether sections filtering is reflected in the 'full spec table' claim, but nothing prevents a correct call.

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%, with the slug sourced from zm_search/zm_list and the sections parameter explained with a Persian example, so the schema already does the heavy lifting. The description adds only a weak implicit contrast between 'full spec table' and the sections filter; 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 and resource ('Get one product's full spec table') and enumerates the returned content: spec table, user score, Zoomit's pros and cons, and price range in Toman. An agent can distinguish it from zm_search/zm_list, though it never names zm_prices or zm_compare, which are the closest content-adjacent siblings.

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 after zm_search or zm_list' is explicit sequencing guidance that tells the agent the slug must come from a prior discovery call, and the schema repeats this in the slug description. There is no when-not guidance (e.g. use zm_compare instead when comparing multiple products), so it falls short of the 5 bar.

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