kafka_read_messages

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

With no annotations provided, the description must carry the burden of disclosing behavioral traits. It does not explicitly state that the operation is read-only (though 'read' implies it), nor does it mention potential side effects like offset consumption or default behavior (e.g., reading from latest). The schema notes defaults, but the description omits them, leaving the agent without warnings about non-obvious behavior.

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 brief and front-loaded: the core action ('Read recent messages from a Kafka topic') appears first, followed by a short use-case note. There is no superfluous wording, but it could arguably be slightly richer without losing conciseness. It remains appropriately sized for the tool's simplicity.

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?

The description does not explain what the tool returns (e.g., a list of message payloads, metadata) nor any caveats like multi-partition handling or default read position beyond what the schema states. For a debugging tool, an agent would benefit from knowing the output format and any limitations. No output schema exists, so the description must cover this gap; it currently does not.

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 input schema already covers all four parameters with clear descriptions (topic required, limit/partition/fromBeginning optional defaults). The description adds no extra meaning about parameter usage, formats, or relationships. Since schema coverage is 100%, the baseline of 3 is appropriate; the description does not detract but adds nothing beyond the schema.

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 states a clear action ('Read recent messages') and a specific resource ('from a Kafka topic'), which differentiates it from sibling tools like kafka_list_topics and kafka_describe_topic that manage topic metadata. It lacks explicit distinction from other read tools (e.g., kafka_consumer_groups), but the phrasing is sufficiently concrete for an agent to infer its core function.

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 provides a usage context ('Useful for debugging event flows') but does not specify when to choose this tool over alternatives. It neither names siblings nor explains when reading messages is preferred over listing or describing topics. The guidance is implied rather than explicit, leaving the agent to infer the right scenario.

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