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

The description explicitly signals read-only behavior via 'Read', discloses the append-only nature of the event hashes, and identifies the scoped capability token as an access requirement. With no annotations available, this gives an agent a meaningful baseline understanding of side effects and auth, though it omits error/expiry behavior.

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?

One sentence, front-loaded with the verb and object, with no redundant words. Every phrase ('one run', 'append-only event hashes', 'scoped capability token') carries information.

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?

Given no annotations and no output schema, the description covers the key inputs and general read behavior, but leaves out return format, failure semantics, and where the capability token comes from. For a simple two-parameter read this is adequate but not complete.

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?

The schema provides no property descriptions (0% coverage), but the description maps run_id to 'one run' and capability_token to 'scoped capability token.' It does not specify formats, token acquisition, or value constraints, so it only partially compensates for the empty schema.

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?

The description names a specific action ('Read') and a specific resource ('one run and append-only event hashes'), making the tool's core function clear. It does not explicitly contrast it with sibling status/capability tools, so sibling differentiation is absent.

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?

There is no guidance on when to use this tool instead of siblings like agentlot_earn_status, gateway_executor_call, or gateway_capability_refresh. The description simply states the operation and provides no exclusions, prerequisites beyond the token, or decision context.

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