list_timelines

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

No annotations are provided, so the description must carry the full burden. It states the tool lists timelines and indicates the active one, which is clear for a read-only operation. However, it does not disclose behavioral traits such as whether it requires an open project or how it handles empty projects, leaving some ambiguity.

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 is front-loaded with the action and clearly states the key outcome (indicating active timeline). Every word adds value, and there is no extraneous information.

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's simplicity (no parameters, likely straightforward output), the description adequately covers the purpose and key output detail. An output schema exists, so return values need not be explained. However, it could mention when it returns an empty list (e.g., no timelines in project) to be fully 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?

The input schema has zero parameters with 100% description coverage, so there is no need for additional parameter details. The description does not add meaning beyond the schema, but the baseline of 4 is appropriate since no compensation is needed.

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 'list' and resource 'timelines,' and adds the important detail that it indicates which timeline is active, clearly distinguishing it from siblings like 'current_timeline' (which returns only the active one) and 'switch_timeline' (which changes the active 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 explicit guidance on when to use this tool vs alternatives like 'current_timeline' or 'switch_timeline.' The context is implied by the purpose, but a mention of when to use this over sibling tools would improve clarity.

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