list_topics

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

No annotations are provided, so the description carries the behavioral burden. It adds useful semantics by explaining that topics relate to opt-out categories, and 'list' implies a read-only operation. However, it doesn't disclose what the response contains, whether topics appear as IDs or names, or any additional constraints.

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 two concise, purposeful sentences with no filler. The main action and resource are front-loaded, and the second sentence provides valuable usage context in minimal words.

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, no-output-schema tool, the description is largely complete: it explains what the tool returns the list of and why that list matters in the broader email-sending workflow. The only minor gap is that it doesn't describe the expected output format, but this is low stakes for such a simple list operation.

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 has zero parameters and the schema properties are empty, so there is nothing for the description to clarify. The description appropriately focuses on the conceptual meaning of the resource rather than inventing parameter behavior.

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 names a specific resource ('subscription topics') and action ('list'), and clarifies what a topic is: a category a person can opt out of individually. This gives the agent a precise idea of the tool's purpose and distinguishes it from generic list operations.

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 explicitly tells the agent when topics are relevant: pass a topic when sending marketing mail so recipients can unsubscribe selectively. It doesn't name sibling alternatives or state when not to use it, but the practical guidance is clear and actionable.

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