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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered and the description need not repeat it. What the description does add is that each entry carries a license and a refresh cadence, which is genuinely useful content-level context given there is no output schema. It says nothing about ordering, count, or whether the source list is static, so the added value is real but modest.

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?

A single sentence that leads with the resource and then the payload contents. No filler, no restatement of the name, nothing that could be cut without losing information.

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, read-only tool with no output schema, the definition covers what is enumerated and what each record contains, which is the information an agent needs to decide to call it. Minor gaps remain around return volume and ordering, but nothing essential 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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The sentence correctly implies the call is unfiltered and global, which is consistent with an empty object schema.

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 pairs a specific verb ("List") with a specific resource ("where the backflow tester data comes from") and names the per-source fields returned (license, refresh). That is far more concrete than the sibling names alone, which are generic list_* tools over unrelated domains. It stops short of explicitly contrasting itself with any sibling, so it lands at 4 rather than 5.

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?

Usage is only implied: an agent can infer this is the provenance/attribution endpoint to call when it needs to cite or verify data origin. There is no statement of when to prefer it over other list_* siblings and no exclusions or prerequisites. With zero parameters there is little room for misuse, which keeps this at an acceptable 3.

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