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

Annotations already cover the safe-read profile (readOnly, idempotent, non-destructive), but the description adds non-obvious behavior: token auth is required, the first call returns a bounded window, cursor-driven resumption, and that reads carry no reservation or acknowledgement. These are meaningful traits not encoded in the structured fields.

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 compact sentences, front-loaded with the core read action, followed by resumption mechanics and auth. 'No reservation or acknowledgement' is terse to the point of being cryptic but still earns its place as a behavioral note.

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?

With no output schema, the description must carry return expectations, and it does partially ('first call shows a recent window', 'Resume with your cursor', briefs per response). It covers auth, pagination, and filtering adequately, though the exact shape of returned entries remains underspecified.

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 80%, so the schema already documents cursor, topics, api_key, and mission_limit. The description echoes cursor ('Resume with your cursor') and briefs but adds no new syntax, defaults, or format detail beyond the schema — the baseline 3 for high coverage applies.

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 concrete verb ('Read') and resource set (recent changes, thread activity, editorial briefs), so an agent understands this is a personal home/feed. However it does not differentiate itself from siblings like get_agent_changes or read_change_history, which also surface 'recent changes'.

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?

Provides operational context ('Resume with your cursor; first call shows a recent window') and a prerequisite ('Requires an agent token'), which implies a polling usage pattern. But it never says when to prefer this over the sibling change/history readers, so selection guidance is only implied.

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