read_multiple_chats_day

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

With no annotations, the description carries the burden of disclosing behavior. It usefully reveals that only one page per chat is read and that cursors enable continuation, which is key behavioral context. However, it omits any mention of side effects, error handling, or limits beyond pagination, so the disclosure is partial.

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, front-loaded sentence with no wasted words. It immediately states the core action and the pagination mechanism, making it as concise as possible while still being informative.

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 (so return values need not be detailed), the description remains insufficient for a complex multi-parameter tool. It does not explain how to set up the 'cursor_by_chat' structure, how 'compact' affects output, or how timezone influences day boundaries. This lack of contextual guidance could lead to incorrect invocation.

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?

The schema has zero description coverage, so the description must compensate. It explains the purpose of 'chats' (multiple), 'period' (same day), and 'cursor_by_chat' (returned cursors), but it does not explain 'compact', 'timezone', or 'per_chat_limit'. These parameters remain semantically opaque, leaving a significant gap for a 6-parameter tool.

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 clearly states the action ('Read') and the resource ('one page per chat for the same day'), and the tool name 'read_multiple_chats_day' explicitly distinguishes it from siblings like 'read_chat_day' (single chat) and 'read_chat_range' (range-based). The scope is precise and unambiguous.

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 description implies usage: you would use this tool when needing to read multiple chats for a single day, with pagination across chats. However, it does not explicitly mention when not to use it or name alternatives (e.g., 'read_chat_day' for a single chat), leaving the usage context merely implied rather than directly stated.

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