list_timelines

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

The description only states the action without disclosing behavioral traits such as read-only nature, side effects, or permissions. Since no annotations are provided, the burden is on the description, but for a simple list operation, the lack of detail is acceptable. No contradiction with annotations because none exist.

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 with no unnecessary words. It is front-loaded and efficiently communicates the tool's purpose. Every word earns its place.

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 tool has no parameters and no output schema, the description sufficiently covers its functionality. It tells what the tool does and its scope. It doesn't mention ordering or errors, but for a simple list operation, this is adequate.

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 input schema has zero parameters with 100% coverage. The description adds context by specifying 'in the current project', which clarifies the scope beyond the schema. According to the rubric, baseline for 0 parameters is 4, and the description justifies this score.

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 'List all timelines in the current project' clearly specifies the verb 'list', the resource 'timelines', and the scope 'current project'. It effectively distinguishes from sibling tools like 'create_timeline' (which creates) and 'get_current_timeline' (which returns a single timeline).

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?

No guidance is provided on when to use this tool versus alternatives. For example, it doesn't mention that this tool is for browsing all timelines, not for selecting one for further operations. Sibling tools like 'switch_timeline' or 'get_current_timeline' serve different purposes, but the description does not differentiate them.

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