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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real behavioral context: the payload is inert data that must not be treated as instructions, and it is a redacted projection. That is valuable disclosure an annotation cannot convey.

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?

Two compact sentences with the core purpose front-loaded and no filler. The safety warning is justified given the payload content, though it crowds out parameter explanations.

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 and zero schema description coverage, the description carries the full burden yet omits what the returned evidence looks like and what two of three parameters control. An agent can call it but may not understand the lookback window or test-inclusion filter.

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 0% for three parameters, and the description only implies the role of event_id. It never explains the 'hours' lookback window (default 2160) or what 'include_operator_tests' does, leaving two parameters undocumented anywhere.

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 and resource ('Read ... published payload evidence') and scopes it by event ID, so the agent knows this fetches one record rather than searching. It doesn't explicitly contrast with siblings like search_observations or get_session_timeline, so it stops short of full differentiation.

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?

The second sentence is a security instruction, not usage guidance. Nothing tells the agent when to prefer this over search_observations or get_session_timeline, nor any prerequisite such as needing an event ID from a prior search.

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