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

Annotations only declare readOnlyHint=true; the description adds the required scope 'pipelines.read', which an agent cannot get from structured fields and which matters for failure prediction. It also discloses the shape of the response (entries vs. recent, including the failure reason on settled entries), though it says nothing about pagination or limits beyond the schema's recent_limit.

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?

Front-loaded with purpose, then return contents, then parameter rules, then auth — a sensible order with no filler sentences. The middle enumeration is dense ('max_cars, auto-admit') and uses internal jargon without glossing it, which costs a little readability.

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 carries the return-value burden and does so by naming the two collections and their fields. Combined with the read-only note, the auth scope, and the identifier rule, an agent has everything needed to call this correctly.

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 schema already documents all seven parameters, which sets the baseline at 3. The description adds the mutual-exclusivity constraint across repository_id/application_id/owner+repo and clarifies that pull_request_number filters to a single PR's history, but leaves provider and recent_limit entirely to the schema.

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 ('Read a repository's Ankra merge train') and then enumerates exactly what the read surfaces: on/off state, max_cars, auto-admit, queued entries with position/status/run, and recently settled entries with reasons. This clearly separates it from siblings like add_to_merge_train, remove_from_merge_train, or enable_merge_when_green.

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?

Gives a concrete addressing rule ('exactly one of repository_id, application_id, or owner and repo') and names the narrowing parameter, which is real usage guidance. It stops short of explicitly pointing at the mutating siblings (add_to_merge_train/remove_from_merge_train) for write operations, so the when-not is left to inference.

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