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

With no annotations, the description carries the burden of behavioral disclosure. It discloses the return format explicitly ({events: [{cursor, event}], next_cursor}) and explains cursor default behavior. It implies a read-only operation via the word 'read' but does not explicitly confirm non-mutability or mention any other side effects, which is a minor gap.

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 sentences with no filler. It front-loads the core action and then adds the key cursor behavior and return format. Every word earns its place.

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 tool has 5 parameters, no output schema, and no annotations. The description explains the return shape and cursor, but omits essential information about required parameters (slug, name) and the 'limit' parameter. An agent would be uncertain how to correctly identify the topic or constrain results, making the description incomplete for safe invocation.

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?

Schema description coverage is only 20%, so the description must compensate. It adds meaning only for the 'cursor' parameter (omit or 0 to start from beginning). It does not explain 'slug', 'name', or 'limit', which are otherwise undocumented in the schema. This leaves critical parameters ambiguous.

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 verb 'read' and the resource 'events from a topic', and specifies cursor-based semantics. It distinguishes itself from sibling tools like topic_publish and queue_fetch by focusing on reading events with a cursor mechanism.

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 gives context on how to start from the beginning (omit cursor or pass 0), but does not explicitly state when to use this tool versus other read-oriented siblings like queue_fetch or discussion_list. No exclusions or alternative routing is provided.

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