What is the user looking at

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

No annotations are provided, so the description carries the burden, and it does disclose the return shape (each selected item with a snippet/title), a freshness field with its exact semantics, and empty-result behavior. It does not state side effects or access requirements, but 'get' plus a read-shaped return makes read-only intent clear.

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, front-loaded with what the tool returns, then the staleness caveat, then the empty case. Every sentence contributes a distinct operational fact with no repetition.

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?

For a zero-parameter, read-only lookup with no output schema, the description covers what is returned, the key freshness signal, and the empty case — everything an agent needs to call and interpret it. No essential gap remains.

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 tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly spends no words on parameter explanation.

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 resource and scope: the entries currently selected by the user in eve's history board, described as the live focus context. This is clearly distinguishable from sibling retrieval tools like eve_recent, eve_search, or eve_get, which fetch raw history rather than current selection state.

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 a concrete interpretive rule — check updated_at, and treat an old value as possibly stale and worth confirming — plus the meaning of an empty items list. It does not, however, name when to prefer a sibling tool such as eve_recent or eve_search instead, so the alternatives dimension is absent.

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