warpline_entity_timeline_get

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

With no annotations, the description carries the full burden. It discloses behavioral traits: returns ordered history, only resolves SEIs, does not claim lineage. However, it omits details like permissions, rate limits, or whether it is read-only, which are expected for a tool with no annotation safety hints.

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 two sentences, front-loading the core purpose and adding a behavioral constraint. No wasteful or redundant language.

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 8 parameters including a nested object, no param descriptions, and no annotations, the description is too brief. While the output schema may document return values, the description does not clarify parameter usage or typical scenarios, leaving significant gaps for the agent.

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 0% and the description provides zero explanation for any of the 8 parameters. The distinction between 'entity_ref' and 'entity' is unclear, and no guidance is given on 'filters', 'sort_by', or 'cursor'. The description fails to compensate for the missing schema descriptions.

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 provides 'ordered change history for one entity ref' with a specific verb and resource. It adds a key distinction: 'warpline reports only whether it resolved a SEI...; it never claims lineage,' which differentiates it from sibling tools like warpline_change_list.

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 does not specify when to use this tool versus alternatives such as warpline_change_list or warpline_entity_churn_count_get. There is no explicit context or exclusion criteria, leaving the agent to infer usage from the purpose alone.

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