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 only reports SEI resolution and not lineage, but it fails to mention ordering criteria, authentication needs, destructive potential, or pagination behavior. The lack of detail leaves significant behavioral ambiguity.

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, concise and front-loaded with the primary purpose. However, it omits essential information about parameters and usage, making it too sparse. Conciseness is achieved at the cost of completeness.

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 (many nested) and a rich set of sibling tools, the description is inadequate. It does not explain entity_ref structure, filter semantics, sorting options, or pagination. The presence of an output schema does not compensate for the lack of input guidance.

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?

With 0% schema coverage, the description should explain parameters but does not. No parameter names or usage are mentioned. The only clue is 'for one entity ref' hinting at entity_ref, but repo, filters, sort, limit, cursor remain unexplained.

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 'Ordered change history for one entity ref,' which clearly indicates the tool provides a chronological list of changes for a single entity. It further distinguishes from siblings by noting that it only reports SEI resolution and never claims lineage, differentiating it from tools like blast_radius or heddle_impact_radius_get.

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 explicit guidance on when to use this tool versus alternatives. The phrase 'for one entity ref' implies single-entity use, but there is no mention of when not to use it or which sibling tools are better suited for multi-entity or lineage queries.

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