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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint, openWorldHint=false), so the bar is lower. The description adds real non-annotation context: the data is private to the person and must never be relayed to third parties. It also bounds the payload size (≤25 topics, ≤5/≤3 lines), though it doesn't discuss freshness or caching.

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?

Purpose is front-loaded and there is no filler, but the single sentence is heavily packed with an enumeration of return fields that largely duplicates the existing output schema. The privacy rule, the most decision-relevant sentence, is buried at the end rather than surfaced earlier.

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?

An output schema exists, so the description needn't enumerate return fields, yet its loose summary is harmless and useful for selection. The privacy constraint fills the main gap that annotations leave open for a personal-data read tool. No pagination or empty-result behavior is mentioned, which keeps it just short of 5.

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. There is nothing for the description to disambiguate, and it correctly implies no filtering arguments are needed to fetch the full topic set.

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+resource (read the person's AI-derived topics) and precisely characterizes the payload: at most 25 topics, each with name, count, recency, landed-in lines, open questions, subtopics and related topics. 'Topics (Ämnen)' is clearly distinguishable from siblings like read_conversation, read_profile or list_personas, which cover raw conversations or static identity data rather than synthesized topic summaries.

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?

It states when to use it ('use it only to help THEM, e.g. to pick up where they left off') and a firm exclusion ('never quote it to anyone else'), which is genuine usage guidance. It does not name an alternative tool for when the agent needs raw conversation data instead (e.g. read_conversation), so it falls short of a 5.

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