get_event_page

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

No annotations are provided, so the description must carry the full behavioral burden. It states that it reads full JSON data and names a precondition, but it omits critical pagination behavior (the limit/cursor defaults of 60000 and 0), error handling, and whether the 'full' data is paged or complete in one response.

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?

The single sentence is front-loaded and free of waste, though for a four-parameter tool with zero schema documentation it is arguably too terse to be 'appropriately sized.'

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 the lack of annotations, no output schema, and 0% parameter coverage, the definition is significantly incomplete. It does not explain how to paginate, what the response format looks like, or how it relates to sibling tools.

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 0% – none of the four parameters have descriptions in the schema. The description mentions a 'journal event' but does not map task_id, seq, limit, or cursor to their meanings or explain their roles.

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 uses a specific verb ('Read') and resource ('full JSON data for a journal event') plus a triggering condition ('data_truncated=true'). It does not distinguish this tool from the related get_events sibling, leaving the agent to infer that this one fetches a paginated slice of a single event.

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?

The condition 'with data_truncated=true' implies when to use the tool, but there is no explicit when-not guidance and no comparison to alternatives like get_events or get_transcript.

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