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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds meaningful extra context beyond the annotations: append-only semantics, pagination, and explicit exclusions (contribution revisions, legacy memory publications). Return shape and page-size behavior are still undisclosed.

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 tight sentences with zero waste; scope and exclusions are front-loaded and the alternative tool is mentioned last. Every sentence 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?

For a read-only tool whose annotations cover the safety profile and which has no output schema, the description is nearly complete: it defines scope, exclusions, pagination, and the alternative. It could note return ordering or page-size defaults, but nothing essential for correct invocation is missing.

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 0%, so the description must carry the load, and it does explain all three: 'paginated' clarifies page, 'optionally limited to one task' clarifies task_id, and 'for a topic' clarifies orbit_id. It stops short of stating defaults or page-size, but the semantic intent of each parameter is clear.

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?

States a specific verb (Read) and a precise resource (paginated append-only task-work and permission event timeline for a topic), and distinguishes itself from the sibling get_contribution_changes. An agent can tell exactly what data this returns versus the broader change feed without opening the schema.

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?

Explicitly routes the agent to get_contribution_changes for the broader change feed, giving a clear alternative with its selecting condition. It also scopes usage by noting what is excluded (contribution revisions, legacy memory publications), though it doesn't spell out a full when-not scenario.

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