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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is covered. The description adds real context beyond that: one topic per answer, the response names tools plus their order and fields, and an omitted topic yields the topic list — useful expectations for a zero-parameter-count-free call. It stops short of anything about result size or formatting.

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 in the first clause and the topic enumeration is compact and scannable. It is somewhat dense with stacked German/English parentheticals and the closing sentence about enabled apps reads as an afterthought rather than a structured part of the answer.

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 single optional enum parameter with no output schema, this is complete: what the tool returns, how granular it is (one topic per answer), what an empty call yields, and an example of the guidance content. Nothing an agent needs in order to call it correctly is missing.

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 coverage is 100% with an enum and per-value description, so the baseline is 3. The description earns above baseline by glossing the semantics of individual enum values (food = logging what was eaten, corrections = Korrigieren, labs = Laborwerte) and by specifying the default behavior when topic is omitted, which the schema does not state.

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 states a concrete deliverable: step-by-step procedures naming tools, order and fields, with an explicit enumeration of the eight supported topics and the no-topic fallback. It is clearly distinguishable from the action siblings (joiva_*, stackwell_*, still_*, vora_*) since none of them return guidance. Minor blur comes from the trailing 'also returns the apps this account has enabled', which is a second, unrelated capability grafted onto the same tool.

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 implied rather than stated: the topic list tells an agent which task families are covered, so it can infer 'ask the guide when the task is one of these'. There is no explicit instruction such as 'call this before attempting an unfamiliar workflow' and no statement of when NOT to use it (e.g. when you already know the tool).

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