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 of behavioral disclosure. It doesn't mention the return format, whether pagination applies, whether it reflects the live cluster state, required permissions, or latency/gating concerns. For a read-only enumeration tool with zero annotation coverage, more behavioral context is warranted.

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, efficient sentence with zero waste. Appropriate for a zero-parameter listing tool.

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 list tool with an output schema present, the description is reasonably complete for its core purpose. However, given the presence of siblings like create_topic, the description could add value by noting this is a read-only discovery operation, and could mention whether topic metadata includes configuration or offsets details.

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, so there is no parameter burden to carry. With schema description coverage at 100% and no params, the baseline of 4 applies. Nothing to add beyond what the schema conveys.

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?

Clear verb+resource: 'List all topics in the Kafka cluster.' This clearly states what it does. The word 'all' suggests it returns the full topic list, distinguishing it somewhat from describe_topic which targets a specific topic.

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?

No guidance on when to use this vs alternatives. With siblings like describe_topic, create_topic, produce_message, consume_messages, the description could note that this is for enumeration/discovery while describe_topic handles individual topic details. No exclusions or context provided.

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