list_topics

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

No annotations exist, and the description is minimal. It does not disclose read-only behavior, potential performance impact for many topics, or response characteristics beyond what the output schema might convey.

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 very short (4 words) and to the point. No unnecessary information exists, though it could benefit from a bit more structure (e.g., a sentence about return format).

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 simple, parameterless tool with an output schema, the description is mostly adequate. However, it lacks context about the scope of 'all' and how it relates to sibling tools like 'get_topic', which could be improved.

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?

There are no parameters, so the description adds no extra semantic value. However, with 0 parameters, the baseline is 4, and the schema coverage is 100%.

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 clearly states the action (list) and resource (Kafka topics). The term 'all' specifies scope, though it could be more explicit about the context (e.g., cluster vs environment).

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 is provided on when to use this tool versus alternatives like 'get_topic'. There is no mention of prerequisites or conditions, leaving the agent without decision-making support.

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