timeline_export

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

No annotations are provided, so the description carries full burden. It only mentions export and lists formats but lacks details on side effects (e.g., file creation), permissions, or blocking behavior. The tool's safety profile is unclear.

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 exceptionally concise with two sentences. It front-loads the primary action and lists export types. While it omits important context, it avoids redundancy and is structurally clear.

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 3 parameters, no output schema, and numerous siblings, the description is too sparse. It does not explain the return value, which timeline is exported, or how to specify non-default timelines. Contextual completeness is low.

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 coverage is 0%. The description lists valid values for export_type, which adds meaning beyond the schema. However, file_path (required) and name_or_handle remain unexplained. The description is insufficient for a 3-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 states 'Export a timeline', clearly indicating the action (export) and resource (timeline). It distinguishes from siblings like timeline_import and timeline_duplicate. However, it does not specify which timeline (presumably current) or the exact output behavior.

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 guidelines on when to use this tool vs alternatives. The description is too brief to provide context on prerequisites or exclusions. Siblings include similar timeline operations but no comparison is offered.

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