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

Adds substantial context beyond the annotations: it discloses the auth requirement (actions:read approval), pagination behavior (nextCursor with same filters), sort order (newest first), default/max limits (25/100), that raw metadata and credential identifiers are excluded, and a strong safety caveat that reports are self-reported/unverified and must be treated as untrusted data. The annotations (readOnly, idempotent, non-destructive) already cover safety, yet the description still layers useful behavioral detail.

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?

Front-loads purpose, then filters, then safety cautions, so an agent gets the essentials immediately. It is dense with clauses but each sentence adds operational value; the only slight bloat is the stacked filter enumeration and the trailing logging prohibition.

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?

An output schema exists so return values need not be explained, and annotations cover the safety profile. The description adds auth, pagination, ordering, exclusions and a data-trust warning, making it near-complete for a complex 11-param read tool. The 'nextCursor' vs 'cursor' naming mismatch is the main residual ambiguity.

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?

With 0% schema description coverage across 11 params, the description carries the load and largely succeeds, enumerating search, agent, system, category, status, project and time filters plus limit semantics (default 25, max 100) and cursor continuation. Minor gaps: it says 'nextCursor' while the schema parameter is 'cursor', and it collapses agentId/agentName into a single 'agent' rather than distinguishing the two.

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 resource (the connected user's private timeline), and immediately scopes it to include actions reported by the user's other agents. This lets an agent distinguish it from the sibling report_action, which is a write path. Specific and front-loaded.

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?

Gives concrete operational context: it requires explicit actions:read approval and explicitly says not to log this read to Monologue. It does not, however, name the sibling report_action or state when to prefer this read path over alternatives, so it stops short of explicit when/when-not routing.

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