list_topics

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

No annotations are provided, so the description carries the full burden. 'List all' implies a non-mutating read and the description adds useful workflow context, but it says nothing about ordering, pagination, empty-result behavior, or auth requirements. Adequate but with clear gaps for a tool whose safety profile is undeclared.

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 short sentences with zero waste; the pipeline position is front-loaded and the follow-on step is stated last, matching the order an agent would reason in.

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 tool with no output schema, the description covers purpose and workflow routing well. Its one gap is that it never says what a topic record contains (e.g. the identifier the agent will need to pass to create_idea), which the absent output schema leaves undocumented.

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 convey and the baseline is 4. The description correctly adds no redundant parameter chatter.

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 all topics') and immediately defines the domain concept ('long-lived content themes'), so the agent knows exactly what is returned. The pipeline framing ('step 1 — Strategy') further distinguishes it from the sibling list_* and create_topic tools.

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?

Gives explicit invocation context ('Start here: the agent picks which topic an idea belongs to') and routes forward to the next step, create_idea (step 2). It lacks any when-not or fallback guidance, so it falls short of the 5 tier.

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