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 without the description. The description adds that the returned AI readings are 'publicly displayed', which usefully signals that it is not the full internal dataset, but says nothing about auth, rate limits, or behavior on a missing entry.

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, front-loaded with the action and output, with a compact example appended. The listing 'labels and publicly displayed AI readings' is slightly ambiguous about whether those are returned fields or contents, which keeps it from a full 5.

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?

This is a simple one-parameter read tool with an output schema, so return values need no explanation and full annotation coverage carries the behavioral load. The remaining gap is routing: it never says when to prefer search_atlas for discovery versus this tool for retrieval.

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 100% and the single parameter already documents that it accepts a domain, HTTPS URL, or sha256 target key from search_atlas. The description's example value ('rupturebrief.com') illustrates the concrete domain form, adding mild value but no syntax or constraints beyond the 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 uses a specific verb ('Read') plus a specific resource ('atlas entry') and names what comes back ('labels and publicly displayed AI readings'), so an agent knows exactly what the tool fetches. It does not, however, distinguish itself from the sibling search_atlas or get_passport, so the differentiation is only implied.

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 when-to-use guidance: no statement about when to call this instead of search_atlas or get_passport, and no prerequisites. The only workflow hint is a single example call, which shows input format rather than selection criteria.

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