timeline_get_items_in_track

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

The annotation readOnlyHint=true already tells the agent this is a safe, non-destructive operation. The description adds that the operation is scoped to a specific track and supports pagination, which is useful behavioral context. It does not mention ordering or behavior on empty tracks, but for a read-only list operation with an output schema present, the level of disclosure is adequate.

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 that states the core purpose and pagination capability without any filler or redundant information. Every word contributes meaning.

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 presence of an output schema, a readOnlyHint annotation, and fully described parameters, the description is nearly complete for this simple list operation. It could mention the returned item structure or any notable behavior (e.g., order of items), but those are typically covered by the output schema. Overall, it provides sufficient context for an agent to select and invoke the tool correctly.

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 already provides 100% description coverage for all four parameters, including defaults and meanings (limit, offset, track_type, track_index). The description adds little beyond what the schema states, so it does not significantly enhance parameter understanding. It correctly implies that 'specific track' relates to track_type and track_index but doesn't go beyond the schema.

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 'List' with a clear resource 'timeline items' and scope 'on a specific track', which distinguishes it from sibling tools like timeline_get_track_count or item_get_duration. It also mentions pagination, which is a key functional aspect not inferable from the name alone.

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 clearly indicates when to use the tool: when you need to list items on a specific timeline track. It does not explicitly name alternatives or exclusions, but the context is clear enough given the focused scope and pagination note. A minor improvement would be to state that this is for browsing items rather than retrieving a single item.

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