List Tracker entity history

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

Annotations already establish readOnly, idempotent and open-world, so the description earns credit for going beyond them: it discloses that results are auto-paginated, that the list is capped at the configured item cap unless `limit` is given, and that each event contains an author, timestamp, display title and individual field changes. This is genuinely useful operational context rather than a restatement of the 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?

Three short sentences, front-loaded with the resource and its auto-pagination nature, followed by return shape and the cap/limit rule. No filler and nothing buried.

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?

There is no output schema, so the description correctly fills that gap by describing what each event carries. Combined with the pagination and cap behavior, an agent has enough to call it correctly; only the routing guidance between this and sibling history/comment tools is missing.

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 every parameter is already documented in the schema; baseline is therefore 3. The description reinforces `limit` ('unless ``limit`` is given') but adds no meaning beyond the schema's own note that omitting it uses the configured cap, so there is little extra value.

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?

States a specific verb and resource: 'An entity's event history (created/updated/commented/…)'. It is clearly distinguishable from write siblings like tracker_entities_update and from the narrower tracker_entities_comments_list, which is called out as one of the event types it subsumes. It stops short of explicitly naming which sibling to prefer when the agent only wants comments.

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 explains the cap behavior under `limit` but gives no when-to-use guidance or alternatives. It never says when to reach for this history list versus tracker_entities_comments_list, tracker_changelog_list, or tracker_entities_get, leaving the agent to infer from the name.

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