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

Annotations already declare readOnlyHint and openWorldHint, and the description adds real context beyond them: the event taxonomy returned, the fact that each event carries a timestamp-precision signal ('how precisely HEY knows its time'), and that results are cursor-paged via 'before'. It stops short of describing ordering direction or what an empty page means.

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-loaded as a question that frames intent, followed by one dense but purposeful sentence on event coverage and lenses, then the paging note. Every clause carries information, though the long run-on enumeration is slightly harder to scan than a short list.

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 an output schema present, return values need not be explained, and annotations cover the safety profile; the description fills in the event taxonomy and paging model that the schema does not. The main residual gap is routing guidance among the several sibling read tools, but nothing needed to invoke it correctly is missing.

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 100% and all four parameters are already documented, including defaults for lens and limit and the cursor meaning for before, so the baseline applies. The description only restates the lens set and the cursor paging, adding no syntax or semantic detail the schema lacks.

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 opening question 'What did this project ship, and when?' plus the enumeration of event types (builds, releases, code, contract deploys, upgrades, locks/unlocks) makes the resource and returned content specific. It does not name or exclude a sibling such as get_changes or get_evidence, so an agent cannot fully distinguish overlapping read tools from the description alone.

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?

It notes 'Lenses: build (default), code, onchain, locks', which implies which lens to pick for which interest, and states paging behavior. However, there is no explicit when-to-use guidance versus get_changes, get_evidence, or explain_fact, and no prerequisites or exclusions are given.

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