clm_list_equipment_timeline

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

Annotations already provide readOnlyHint and idempotentHint, covering the safety profile. The description adds generic 'filtered, searched, sorted, and paged' claims but does not explain how search and sorting are controlled, especially since no such parameters exist in the schema. It does not contradict the annotations.

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 the verb and resource front-loaded and a compact tail describing capabilities. There is no filler, redundant restatement of the tool name, or extraneous detail.

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?

With a full input schema, output schema, and read-only/idempotent annotations, the description covers most of what an agent needs. The missing piece is clarity around the claimed 'searched, sorted' behavior, since an agent may look for search/sort parameters that are not present in the schema.

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%, so the input schema already documents all six parameters, including the required schedule date window, pagination, and site_id default. The description adds no additional parameter-level meaning beyond high-level 'filtered, searched, sorted, and paged' phrasing.

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 identifies the resource ('equipment timeline entries (bookings)') and the intended view ('cockpit equipment list view'), distinguishing it from siblings like clm_list_equipment and clm_get_shipment_timeline. However, it also claims the tool supports 'searched, sorted' behavior, but no search or sort parameters exist in the schema, introducing slight imprecision.

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 phrase 'for the cockpit equipment list view' gives useful context, but the description does not state when to use this tool versus alternatives such as clm_list_equipment or clm_get_shipment_timeline. No explicit when-to-use or when-not-to-use guidance is provided; usage must be inferred from the name and sibling context.

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