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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint=false), and the description still adds real behavior: default 25/max 100 page size, newest-first ordering, the 500-row public API cap, and cursor stability rules ('pass nextCursor unchanged; restart without a cursor if the timeline changed'). It does not say how the caller detects more pages or what happens with an expired/invalid cursor.

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?

Six tight sentences, front-loaded with what the tool is, then ordering, semantics of contrast, pagination, and the API cap. Every sentence carries information and nothing is padded.

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 read-only paginated list tool with no output schema, the description covers ordering, page size, cursor lifecycle, and the row cap, which is most of what an agent needs. It leaves unstated whether the response exposes a next-page cursor and what the event records contain, so completeness is strong but not airtight.

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 only 33% (only slug is documented), so the description must compensate, and it does for cursor: it explains to pass the cursor unchanged and to restart without one if the timeline changed. It also restates limit bounds (25/100) that the schema already enforces; the parameter name mismatch ('nextCursor' in text vs 'cursor' in schema) is a minor friction.

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?

Names a specific verb and resource ('page the public dated event timeline') plus ordering ('newest event date first'), so the agent knows exactly what is returned. It differentiates the resource from recording/notification feeds ('not private monitoring notifications or a since-last-run feed'), but never distinguishes itself from the sibling get_builder_timeline, which sounds closely related.

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 clear context of use (retrieving historical recorded events rather than live/since-last-run notifications) and an explicit exclusion of what this tool is not. It stops short of naming the sibling tools or stating when an agent should prefer get_builder_timeline or search_builders over this one.

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