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

Annotations already cover the safety profile (readOnlyHint, openWorldHint). The description adds real behavioral context beyond them: results carry a time-precision signal ('how precisely HEY knows its time') and the response is paginated via the before cursor returned by each answer. It stops short of stating rate limits or auth requirements.

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 dense sentences, front-loaded with the resource scope before the lens and pagination details. Every clause carries information, though the first sentence is a long comma run that could be tightened.

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, the description carries the return-value burden and does so partly: it names the event categories, the per-event time-precision metadata, and pagination. An agent can call it confidently, with only the missing default-limit detail (already in the schema) and lens-selection logic left unaddressed.

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 75% (slug, limit, before documented in the schema). The description meaningfully adds to the one undocumented param by enumerating the lens values and tying them to event categories, and it explains the before cursor's origin. It says nothing extra about slug or the default limit.

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 verb ('One project's research timeline') and enumerates the event types it aggregates: builds, releases, code, contract deploys, upgrades, token verification, locks, unlocks. It is distinguishable from siblings like get_changes or get_project_snapshot by that enumeration, though it never explicitly names an alternative.

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?

No when-to-use, when-not-to-use, or alternative routing. The listed lenses (everything, build, code, onchain, market, locks) hint at scope selection but the description never says which lens suits which question or when to prefer this over get_changes/project_diff. Guidance is entirely left to inference.

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