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

The annotations already declare readOnlyHint=true, and the description's verb 'List' reinforces the read-only nature. It adds the API endpoint 'GET /jurisdictions' and specifies the data elements returned, which is useful given the absence of an output schema. No contradictory behavioral claims are made.

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 two short sentences with no filler. The main purpose and return fields are front-loaded, and the API endpoint is presented as a separate, compact detail that does not distract from the core description.

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 no-parameter, read-only list operation, the description is complete: it identifies the resource, its scope, the returned fields, and the HTTP endpoint. Since there is no output schema, the explicit field list compensates; no critical information 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?

The tool has zero parameters, so there is nothing to document; the schema coverage is trivially 100%. The description still adds value by explaining the output fields rather than parameters, which is the relevant semantic content here.

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 starts with a specific verb 'List', names the resource 'tax jurisdictions', enumerates the returned fields (id, name, country, region), and defines the scope 'where the account is registered to collect tax'. This clearly differentiates it from sibling list_* tools such as list_tax_codes.

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?

The description states a clear context for use: when the account's registered tax jurisdictions are needed. It does not explicitly contrast with alternatives like list_tax_codes, but the scope statement gives enough guidance to select this tool over generic list operations.

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