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

Annotations already declare readOnly=true, idempotent=true, and non-destructive, so safety is covered. The description adds one genuinely new trait, 'Free', which is cost behavior not captured in annotations. It does not disclose scope of what 'coverage' means or any rate/access constraints.

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?

Two short sentences with no filler, and the key differentiator ('Free') is front-loaded. Efficient, though terse enough to leave gaps the agent must fill on its own.

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?

An output schema exists so return values need no explanation, and the tool is a simple read. However, with three callable parameters and zero schema documentation, the description should at least say how city/state and jurisdiction_id relate, which it does not.

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 description coverage is 0% and the description mentions no parameters at all, so city, state, and jurisdiction_id are entirely undocumented. In particular the interaction between passing city/state versus jurisdiction_id is a real ambiguity with no guidance.

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+resource ('Return jurisdiction and source coverage') and frames itself against paid research. An agent can tell it is a free coverage-lookup without opening the schema, though it is not sharply distinguished from the nearby get_source_catalog sibling.

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 phrase 'without running paid research' implies this is the cheap pre-flight option, but no explicit when-to-use or when-not-to-use guidance is given relative to siblings like get_source_catalog or resolve_jurisdiction. Usage is inferable, not stated.

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