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

The annotations already establish readOnlyHint=true, so the trailing 'Read-only' is largely a restatement. What the description genuinely adds is behavioral: the ordering is newest-first, and each event carries a status and timestamp. It does not cover volume/pagination behavior or any auth prerequisites, which keeps it below 5.

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?

Two sentences, front-loaded with the resource and its contents, with the usage hint and read-only note trailing. No filler; every clause adds information.

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 no output schema, the description usefully enumerates return content, ordering, and per-event fields, which is what an agent needs to interpret results. The only gap is that it does not mention truncation/paging relative to the limit parameter, though the schema itself documents the default and cap.

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% – limit (default 60, max 100) and application_id are both documented in the schema. The description adds no additional meaning about either parameter, so the baseline 3 applies.

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?

Specific verb+resource ('Get an Application's recorded history') plus an explicit enumeration of what the history contains (created, setup PR merged, platform builds, deploy runs, demo previews, AI reviews) and the sort order. This clearly separates it from siblings like get_application_deployments, list_application_pull_request_reviews, and resource_timeline.

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?

'Use this to answer what happened and when' gives a clear positive use context. However, it never names an alternative or an exclusion (e.g., when to prefer get_application_deployments or resource_timeline for a narrower/more general view), so the routing guidance stops short of explicit when-not.

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