timeline

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

With no annotations provided, the description carries the full burden of disclosing behavior. It does disclose that the tool returns a single bounded page and requires cursor-based looping, which is valuable. It does not mention read-only nature, side effects, or error behavior, but the verb 'Read' implies a safe read operation, providing a baseline level of transparency.

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 description is a single sentence that front-loads the core action ('Read one bounded timeline page') and immediately follows with the essential loop instruction. Every word earns its place, and there is no redundancy or irrelevant detail.

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?

Although an output schema exists, the tool has 14 optional parameters and no parameter descriptions. The description only covers the pagination loop and does not explain what filters (chat, sender, keyword, message_type, etc.) do, how ordering works, or how the cursor interacts with before/after parameters. For a tool this complex, the description is far from complete.

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%, and the description adds no explanation for any of the 14 parameters. The only mention is of the response field 'data.page.next_cursor', not input parameters. With no parameter semantics provided, an agent would have to infer the meaning of fields like 'after_message', 'display_order', or 'compact' from names alone, which is insufficient.

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 the specific verb 'Read' on the resource 'bounded timeline page' and explicitly mentions the pagination pattern, clearly distinguishing it from sibling read tools that likely fetch ranges, days, or events. The scope is precise: one page at a time, loop until done.

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 gives a clear usage instruction to loop with data.page.next_cursor until done, which is strong contextual guidance for iterative pagination. However, it does not explicitly name alternatives (e.g., read_chat_range) or say when not to use this tool, so it earns a 4 rather than a 5.

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