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

The annotations already declare readOnlyHint=true, so the read-only safety profile is covered. The description adds useful scoping information ('your') indicating the result is limited to the current user's followed topics, but it does not disclose return format, ordering, pagination, or other behavioral details. This is acceptable for a trivial zero-parameter tool but adds only modest value beyond the annotation.

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?

The description is a single short sentence with no filler or redundant phrasing. The verb and object are front-loaded, and every word contributes to meaning.

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-only listing tool, the description is largely sufficient: an agent knows to call it with no arguments and expects a list of followed topics. The only gap is the absence of an output schema and no mention of what fields each listed topic contains, which would improve completeness but is not blocking for correct invocation.

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 input schema has zero parameters and the schema description coverage is 100%, so there is no parameter-level semantics for the description to clarify. Per the rubric, zero-parameter tools get a baseline of 4. The description adds nothing needed here.

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 ('List') and a clear resource ('your followed topics'), making the tool's purpose immediately obvious. It also distinguishes itself from sibling list tools like list_questions and list_rooms by naming the unique resource. There is no ambiguity about what the operation returns.

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 implies the use case: call this when you need to see the topics the current user follows. However, it gives no explicit guidance about when not to use it or how it compares to alternatives like follow_topic or get_inbox. Usage context is present only by implication.

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