get_timeline

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

No annotations are provided, so the description carries full burden. It discloses that the tool returns detailed data including eventContent, status, metadata, and context, which helps understand the return structure. However, it doesn't mention error conditions, authentication requirements, rate limits, or whether the operation is idempotent, leaving behavioral gaps for a read operation.

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 perfectly concise with two sentences that each serve distinct purposes: the first states the core functionality, and the second provides usage guidance. There's no redundant information, and it's front-loaded with the primary action.

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?

For a read operation with 3 fully documented parameters and no output schema, the description provides good context about what data is returned and when to use the tool. However, without annotations or output schema, it could benefit from more detail about error cases or response format specifics 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?

Schema description coverage is 100%, providing complete parameter documentation in the structured schema. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., it doesn't explain parameter relationships or provide examples). With full schema coverage, the baseline score of 3 is appropriate.

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 specific action ('Get a single timeline by ID') and resource ('timeline/step execution record'), distinguishing it from sibling tools like list_timelines (which lists multiple) and get_execution (which focuses on execution-level data). It specifies that this tool retrieves detailed step-level information.

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 explicitly states when to use this tool ('to inspect a specific step's result in detail'), providing clear context for its application. It implicitly distinguishes from alternatives like list_timelines (for browsing) and get_execution (for broader execution data) by emphasizing single-item detail retrieval.

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