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

The key disclosure is 'NOTHING is saved', which is exactly what an agent needs given readOnlyHint=false and destructiveHint=false — it prevents mistaking this for a persisting mutation. It also explains the deterministic-first, then AI matching order and that AI is only used when available and useAi is not false. Minor gap: it does not say how many AI calls or how large a mapping table to expect.

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?

Purpose and the no-save constraint are front-loaded, with options collected at the end after 'Options:'. The middle sentence is very dense with parentheses and nested clauses, which slightly hurts skimmability, but no sentence is filler.

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 still tells the agent what comes back (a mapping table plus a ready-to-save rule definition keyed on productType) and what to do next. Nothing material for correct invocation is missing.

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 100%, so baseline is 3, but the description adds interaction semantics the schema states separately: onlyMissing scopes the rule to items with no category yet, and defaultCategory applies to productTypes absent from the table. It also clarifies the useAi fallback ordering.

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 (propose a googleProductCategory mapping) and resource (feed items grouped by productType), and names both the matching strategy and the output artifact. It is clearly distinguishable from siblings like create_rule (persists) and search_taxonomy (resolves individual paths).

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 end-to-end workflow: show the human the mapping, resolve unmatched types with search_taxonomy, then save with create_rule which runs preview and returns the impact report. It also names the condition for scoping (onlyMissing=true) versus the default behavior of fixing wrong existing values.

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