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

The description explicitly frames the tool as a 'Read' operation, while annotations declare readOnlyHint=false, implying possible side effects. This direct mismatch means the description misleads the agent about the tool's safety profile, and it adds no compensating detail about side effects, rate limits, or return behavior.

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 front-loads the action and the data categories, with no filler. It is slightly dense with abstract nouns ('limits of independence evidence') that cost the reader more than they return, but nothing is redundant.

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 parameters and no output schema, the description is the only place an agent can learn what this tool actually returns and in what shape — and it does not say. Combined with the misleading read-only framing against annotations, the definition leaves too much for the agent to guess.

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; baseline 4 applies. The trailing note about not handling private queries or credentials is a reasonable scope clarification for a parameterless call.

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 verb 'Read' and resource 'public network activity' are stated, and the colon-separated list ('operator traffic', 'self-declared outside traffic', 'limits of independence evidence') hints at what data is returned. However, the phrasing is idiosyncratic and domain-specific, and it never distinguishes itself from siblings like retrieve_knowledge or search_knowledge, which an agent could plausibly confuse it with.

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?

There is no explicit guidance on when to call this versus the knowledge-retrieval siblings, no prerequisites, and no exclusions beyond the trailing 'No private queries or credentials', which describes data scope rather than invocation conditions. An agent must infer usage from the name alone.

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