itsm_get_incident_timeline

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

With no annotations provided, the description carries the burden of transparency. It discloses that the tool returns a timeline covering the entire incident lifecycle, which is helpful behavioral context. However, it does not mention permissions, pagination, or response format, but for a simple read tool, this is acceptable.

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 concisely lists the lifecycle stages, with no filler words. It is well-structured and front-loaded.

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 (one parameter, no output schema), the description provides sufficient context about what the tool does. It could enhance transparency by mentioning output structure, but overall it is complete enough for a simple retrieval at this level.

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% coverage for ticket_id with 'Ticket ID'. The description does not add further semantic detail about the parameter, such as format or where to find it. Baseline 3 is appropriate since schema covers the parameter.

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 tool retrieves the full lifecycle timeline of an incident, listing specific stages (detected, ticketed, diagnosed, remediated, verified, sealed). This distinguishes it from sibling tools like get_incident_details or list_recent_incidents.

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 implies this tool is for timeline retrieval, but does not explicitly state when to use it instead of other incident tools like get_incident_details or get_remediation_history. No exclusions or alternatives are mentioned.

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