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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds a genuinely behavioral point beyond that: each source carries limitations and retrieval status, warning the agent that ingested data may be partial or stale and that it should qualify coverage claims accordingly.

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 sentences, zero filler. The returned-field summary comes first so the agent learns what it gets before the usage hint, which is the right front-loading for a zero-arg list tool.

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 must sketch the return shape, and it does so by enumerating the per-source fields (scope, limitations, status, last success, counts). Slightly more detail on whether results are paginated or how many sources typically return would make it complete, but it is sufficient to call correctly.

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 no parameter semantics burden; baseline 4 applies. The description correctly does not invent arguments or filtering options.

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 the specific resource (every source KEVWire ingests) and the fields surfaced for each (scope, limitations, retrieval status, last success, record counts), which is far more than a restatement of the name. It does not explicitly contrast with siblings like list_technologies or get_record, but the resource is unambiguous enough to route on.

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?

"Use this to describe coverage honestly" gives a directional hint about the intent (coverage reporting) but not a concrete trigger condition, prerequisites, or named alternatives. The agent can infer it is the discovery/status entry point, but that is inference rather than guidance.

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