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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description usefully adds the ranking criteria (severity, simulation evidence strength, wait time, run volume), but says nothing about pagination, limits, or freshness beyond what the schema states.

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-loads the resource and scope in the first sentence, with ranking detail second. The trailing list of paraphrased user questions is somewhat redundant filler, but overall it is tight.

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 carries the burden of describing returns and does so — pending PRs/deployments, their priority ordering, and what the ordering is based on. Missing only edge behavior like what happens when the queue is empty or how items expire.

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% and all three parameters (limit, agentId, customerId) are documented in the schema, including defaults, maxima, and the superadmin restriction. The description adds no parameter information, so 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?

Names a specific resource and scope: a prioritized list of pending optimization PRs/deployments needing human review. Clear verb+resource, but it does not distinguish itself from nearby siblings like list_pending_approvals, get_adjudication_queue, or get_review_case.

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 quoted user questions ('what should I review?', 'any pending PRs?') imply when to reach for it, but no explicit when-not conditions or alternative tools (e.g. get_adjudication_queue vs. list_pending_approvals) are offered.

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