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

Annotations already cover the safety profile (readOnly=true, destructive=false, closed world), yet the description adds real value: it discloses that shared rates and ungrouped rates are reported and that these 'change what an edit will do'. It doesn't discuss volume/pagination, but for a zero-param settings read that is minor.

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 resource and its contents, then the critical 'call this first' rule, then the group-membership caveat. It is somewhat dense with quoted example questions, but every sentence carries actionable information and nothing is redundant.

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 carries the return-shape burden and does so thoroughly (groups, ordered rates, per-outlet percentages). Read-only status is stated and preconditions (must be called before id-consuming tax tools) are given, so nothing an agent needs to call it correctly 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?

Zero parameters, so the baseline is 4. The description still adds useful semantics by clarifying which id families originate here (tax group ids, tax rate ids, outlet ids) and that names are not accepted elsewhere.

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?

Names a specific verb+resource ('hub_get_taxes' = read the whole Settings → Taxes screen) and enumerates exactly what it returns: tax groups, rates in charging order, and per-outlet percentages. It is unmistakably distinct from sibling list/read tools like hub_get_outlets or hub_get_tax_* mutations.

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?

Provides explicit sequencing ('ALWAYS call this before any other tax tool') and the reason (every other tool takes ids from here and none accept names). It also lists the concrete questions it answers, giving the agent clear selection criteria.

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