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

With readOnlyHint already declaring safety, the description adds useful behavioral detail: null category meaning, the dashboard's specific definition of missingOnly, and server-side pagination with limit/offset and total returned. It does not cover auth or rate limits, but those are not central here.

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 front-loaded with the resource and row shape, then explains missingOnly, gives the intended use, and ends with pagination. Every sentence carries useful information with no 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?

For a six-parameter read-only worksheet tool with no output schema, the description explains the returned row shape, the special missingOnly semantics, the intended downstream use, and pagination. Remaining gaps like account-filter behavior and reason are adequately covered by the schema.

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 67%, so the schema handles region, accounts, and reason reasonably well. The description adds real meaning for missingOnly by explaining the dashboard's precise missing-definition, and it clarifies limit/offset pagination and total returned.

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 states precisely what the tool returns: one VAT region's worksheet with a row per (account, ASIN, SKU) sold product and its current category. It distinguishes itself from downstream import_vat_categories by framing the worksheet as the input used before building import rows.

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?

It gives a clear use case—matching a seller's tax-class file to exact SKUs/ASINs before constructing import_vat_categories rows. It does not explicitly name when not to use it or list alternative tools, but the context is concrete.

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