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, so the safety profile is covered by structured data. The description adds genuinely new behavioral context beyond that: every result includes canonicalUrl and the author entity Alicia (Person @id), and it flags a domain trap (3D garden, not a wiki). It stops short of describing pagination or result-size behavior.

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?

Four short sentences that front-load the core purpose and return contents. The trailing 'not a knowledge-base wiki' sentence is somewhat tangential to the tool's mechanics, but it is short and plausibly prevents misrouting, so only minor waste.

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 return values need not be re-explained, yet the description usefully highlights the two guaranteed fields an agent must act on (canonicalUrl, author). With annotations covering the safety profile and the schema covering the parameter, little an agent needs to invoke this 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?

There is a single optional parameter and schema description coverage is 100%, with the enum semantics ('zh and zh-CN both mean Chinese') fully documented in the schema. The description adds nothing about the language filter, so the baseline 3 applies.

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?

States a specific verb and resource ('List topics used by the published notes') plus the scope of the result set (with article counts and canonical URLs). The resource 'topics' is unambiguous against siblings get_article, list_recent_articles, and search_articles, which all operate on articles, so an agent can route correctly.

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 gives downstream usage guidance ('cite the canonical URL when quoting') and warns the agent not to treat digitalgarden.si as a knowledge-base wiki, but it never states when to choose list_topics over search_articles or list_recent_articles. Usage is implied rather than explicit, which is the minimum-viable level.

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