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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile needs no restating. The description does add useful behavioral value by disclosing what each entry contains (published description, premise, note slugs). It says nothing about result size, ordering, or whether all topics are always returned, which matters for a no-parameter listing.

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?

A single sentence, front-loaded with the action and resource, then the returned fields. No filler, no redundancy with the title or annotations.

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?

With no output schema present, describing the shape of each returned item is the right thing to include, and the description does it. The remaining gap is the absence of any note about result volume/ordering or that the listing is unfiltered and unpaginated, which an agent would want before relying on it.

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 semantics to explain beyond the implicit no-filter behavior. Baseline 4 applies; the description correctly does not waste space on nonexistent inputs.

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?

Specific verb + resource ("List the topic guides") that is clearly a different resource from the note-oriented siblings (get_note, latest_notes, search_notes, related_notes). It also enumerates the returned fields, so an agent knows this is a browse/enumerate operation. It stops short of explicitly contrasting itself with the note tools, so a 4 rather than a 5.

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 statement of when to call this versus the note tools, no prerequisites, and no exclusions. Usage is only inferable from the verb "List"; the description never routes the agent between this and search_notes or get_note.

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