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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context by explaining that entries are background continuations of timed-out synchronous calls. It omits ordering, retention window, and how long a background entry remains retrievable.

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?

A single front-loaded sentence with zero filler, and the distinguishing qualifier arrives before any trailing clause. It is arguably too short for the gaps it leaves, but per conciseness criteria nothing is wasted.

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?

For a tool whose whole point is discovering backgrounded calls, the description omits the lifecycle: how entries are identified, whether they expire, and what the agent should call next to obtain results. Annotations cover safety but not these operational facts, and there is no output schema to lean on.

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 0% — the single 'limit' parameter has no description, only default 20 and min/max bounds. The description does not mention 'limit' at all, so it adds nothing to clarify whether it caps returned entries and how ordering interacts with truncation. With low coverage the description was expected to compensate and does not.

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 (List) and resource (Remote MCP calls) and qualifies the scope precisely as calls that 'exceeded the bounded synchronous wait and continued in the background.' This is much sharper than the title alone. However, it never distinguishes itself from the closely-named sibling get_recent_tool_calls, leaving an agent to guess which list it wants.

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 when-to-use or when-not-to-use guidance is given, and no sibling is named. Critically, the description does not say to follow up with get_tool_result (or get_recent_tool_calls) to actually retrieve results or to compare the two lists, which is the obvious next step for an agent.

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