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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds non-obvious behavior beyond annotations: this is a full unfiltered enumeration intended as an upfront discovery/caching call, and the ids it returns are reused by other tools. It does not mention whether the list is bounded or truncated.

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?

Three tight sentences, front-loaded with what it returns before moving to usage imperatives. Every sentence earns its place by adding routing or workflow information not present in structured fields.

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 enumeration tool with an output schema and full annotation coverage, nothing an agent needs is missing. Workflow placement (call first), id reuse, and the unit-conversion constraint are all stated.

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 no parameters, so there is no parameter semantics to document - baseline 4 applies. The field list in the description describes the return payload rather than inputs, and an output schema already exists.

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 (lists every topic the person tracks) and enumerates the returned fields (id, type, unit, goal, entry count, last entry time). An agent can distinguish it from siblings like list_dashboards or get_dashboard without opening the schema.

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?

Explicitly prescribes when to call it (once at the start), what to do with the result (remember the ids), and the alternative to avoid (creating a near-duplicate topic instead of reusing an existing one - routing to create_topic/update_topic). It also flags the downstream workflow constraint to convert values into the topic's unit before logging, pointing at log_entry.

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