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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds valuable behavioral context by specifying exactly what the DTO includes (categorical, thresholded aggregates) and excludes (raw edges, private capabilities, aliases, etc.), which is not covered by annotations. This goes beyond the structured metadata.

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?

The description is two sentences with no superfluous content. The primary action and resource are front-loaded, and the second sentence efficiently lists exclusions. Every phrase earns its place, making it highly concise and well-structured.

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 parameterless tool with an output schema, the description fully explains what the agent will receive: the latest frozen public DTO with specific aggregate cells, and explicitly lists unavailable data. There is no missing critical information needed to decide whether to call this tool or interpret its result.

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 has zero parameters, so the schema is trivially complete. Per rubric, a baseline of 4 applies, and the description further enriches the context by describing the nature of the DTO, even though it doesn't cover parameter details (there are none). This is acceptable and exceeds the baseline.

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 clearly states the verb ('Return'), the resource ('the latest already-frozen public Connection Atlas DTO'), and its scope ('only' and 'already-frozen'). This is distinct from the sibling tools, which deal with ballots, friendship, and personality, so there is no ambiguity about what this tool does.

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 description does not provide any explicit guidance on when to use this tool versus alternatives, nor does it mention any exclusions or prerequisites. While the tool's name and content make its purpose obvious relative to the unrelated siblings, there is no 'use this when' or 'use that instead' language, leaving usage inference entirely to the agent.

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