Account overview and reading statistics

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

With no annotations supplied, the description carries the full behavioral burden; it does disclose the safety profile ("Safe read-only overview") and reveals that poll failures appear in the output, which is genuinely useful diagnostic context. It does not mention cost/latency of an aggregation across all feeds, data freshness, or how counts are bounded (e.g., how many top feeds are returned), so disclosure is partial.

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, front-loaded with the core action, and the long enumeration is justified because each listed metric tells the agent what it can avoid calling other tools for. The closing safety note is short and useful.

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 zero-parameter read tool with no output schema, the description usefully compensates by naming the fields in the response. It stops short of describing the response shape (counts vs. objects, whether top feeds are ranked, how many are included), which is the remaining 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 there is no parameter meaning to add; the baseline for a no-param tool applies. The description correctly implies no inputs are required, consistent with 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 uses a specific verb and resource ("Returns account-wide statistics") and then enumerates exactly which metrics come back: subscribed feeds, unread totals, saved counts, top feeds, folder unread counts, and poll failures. That enumeration makes its role distinct from list_feeds, list_folders, and get_digest, though no sibling is named 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?

There is no explicit when-to-use guidance, no exclusions, and no reference to alternatives such as get_digest or list_feeds for agents that want a narrower slice. The purpose implies a dashboard-style summary, but the agent must infer that on its own.

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