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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, which are comprehensive for a read-only list operation. The description adds the meaning of the returned data (publication date, last checked), but since there is no output schema, this is valuable. No contradictions.

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?

One sentence, concise, and front-loaded with the action ('List every jurisdiction') and the output details. The usage hint is at the end, but the sentence is short and focused. No fluff.

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 zero-parameter tool with rich annotations (read-only, open world, idempotent), the description fully covers what the tool does and when to use it. The output schema is absent, but the description lists the key fields, so an agent knows what to expect. The complexity is low, so nothing 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 the description doesn't need to explain any. The description adds contextual meaning about what the list contains and its purpose, which is beyond the empty schema. This is appropriate.

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 clearly states the verb 'list' and the resource 'jurisdictions and official registers', and specifies the key output fields (publication date, last checked time). It also explicitly says 'Call this first to learn coverage and freshness', which distinguishes it from the sibling tools that deal with changes and funding programs.

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 explicitly instructs the agent to call this tool first to learn coverage and freshness, which is a clear usage directive. It doesn't explicitly mention alternatives, but the siblings (changes_since, get_regulatory_change, search_funding_programs, search_regulatory_changes) are implicitly different, so the purpose is unambiguous.

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