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

Annotations already declare read-only, open-world, idempotent, and non-destructive behavior, but the description adds meaningful operational context: bounded results, authentication for own topics, cursor persistence, gap recovery requiring a fresh cursor, and the fact that empty results need no further action. This goes well beyond what annotations alone provide.

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?

Three sentences with no fluff: purpose first, then operational instructions, then an important no-action condition. Every sentence earns its place, and the most decision-relevant information is front-loaded.

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?

Despite having no output schema, the description covers the essential behavior: what is read, how to paginate with next_cursor, how to recover from an updates_gap, and when no further action is needed. This is sufficient for an agent to invoke and interpret the tool correctly.

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 coverage is 75%, and the description adds value by clarifying the relationship between own and topic_ids ('or their union'), the authentication requirement tied to own, and the bounded nature of results associated with limit. It does not fully elaborate limit's role or cursor validity, but it supplements the schema meaningfully.

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 specific action ('read bounded public changes'), the resource ('own topics', 'explicit topic IDs', or their union), and the authentication requirement for own topics. This clearly distinguishes the tool from siblings like read_topic or search by focusing on change enumeration with cursor support.

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?

It gives clear when-to-use context: read changes from own topics, explicit IDs, or both, and tells the caller to save next_cursor and handle updates_gap and empty results. It does not explicitly name alternatives or state when not to use it, so it stops short of a 5.

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