Archive overview

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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds useful scope context (it reports counts, date coverage, tags, and import recency), but does not say whether these are cached snapshot values or freshly computed, or roughly how large the response is. That is reasonable but not rich added disclosure.

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 compact sentence that front-loads the core answer ('what the archive holds') and then lists the specific fields. No filler, no repetition of the tool name or title; only minor gain from splitting the enumeration into a readable list.

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?

There is no output schema, so the description must carry the return-value burden, and it does by naming the four things returned. For a zero-parameter, read-only summary tool that is essentially complete; only the lack of guidance on when to call it leaves a small gap.

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 the baseline is 4. The description correctly makes clear there is nothing to filter or configure - it is a whole-archive summary - which matches the empty 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 gives a specific verb-plus-resource ('what the archive holds') and enumerates the exact contents: per-platform chat counts, covered date ranges, tags in use, and last import date. That enumeration separates it from chat-level siblings like list_chats and read_chat, though it never names them explicitly.

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: the contents described suggest it is an orientation/first-call tool, but the description never says 'call this before searching' or when to prefer it over search_chats or list_chats. No exclusions or prerequisites are stated.

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