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

Annotations already declare readOnly/openWorld/non-destructive, so the floor is low, yet the description adds genuine behavior: the evidence is unsigned and timestamped, it explicitly does not certify safety, and api_key is required for owner attribution. The only real omission is any note on pagination or rate limits for what is clearly a feed.

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 the core purpose front-loaded, and the caveat and auth requirement are appropriately placed. The second sentence ('Check stale, provisional, open_incident and incidents_truncated') lists output field names without context, and the final clause about owner activation is grammatically convoluted.

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-value detail is unnecessary, and the description covers purpose, an explicit non-guarantee, and auth requirements. It is close to complete for a read feed, with only the relationship to closely-named siblings left implicit.

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 parameter burden. It does explain the non-obvious api_key semantics (owner-scoped, required unless publicly shared, used for attribution on scheduled-check retrieval), but says nothing about agent_id beyond what the schema name implies.

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 (unsigned, timestamped operational evidence and recent incidents), and the word 'unsigned' implicitly distinguishes it from the sibling agent_signed_evidence. It doesn't name any sibling explicitly, so the differentiation is only inferable rather than stated.

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?

'before a trust decision' gives real situational context for when to call it, and the 'does not certify agent safety' caveat signals a boundary. However, it never says when to prefer this over the very similar siblings (agent_health_status, agent_health_checks, agent_signed_evidence), so an agent must guess between them.

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