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

Annotations already establish readOnly/openWorld/idempotent, and the description adds real behavior beyond them: jurisdictions resolve through an approved regulator registry, records from non-approved authority domains are excluded, missing/unavailable states are surfaced explicitly, and results are research rather than legal advice. Data-provenance and failure-mode disclosure like this is exactly what annotations cannot express.

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?

Three compact sentences front-loaded with the core action, followed by provenance rules, disclaimers, and an example. Every sentence adds distinct information (scope, filtering, edge cases, invocation shape) 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?

With no output schema, the description carries the return-value burden and does partially: it promises context plus enforcement records and explicit missing/unavailable states. It does not describe the shape of an individual enforcement record or how results are ordered/paginated, which leaves a modest gap for an open-world research tool.

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 only 50% (limit has no description, just bounds/default), and the description compensates: it supplies a concrete example payload and clarifies that omitting jurisdiction yields a bounded global list, implicitly explaining limit's role. It stops short of explaining the 1-25 range semantics or what a larger limit trades off.

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 gambling regulatory context for a jurisdiction plus recent source-linked enforcement records.' It also scopes the output domain (regulatory/enforcement), which cleanly separates it from the casino-listing and bonus siblings. An agent can identify what this returns without opening the schema.

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 a clear usage condition: supply a jurisdiction for targeted lookup, or 'Omit jurisdiction for a bounded global list.' That covers the main branch of when to use it. No alternative sibling is named, but none of the listed siblings serve regulatory research, so the omission is minor rather than a gap.

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