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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description's only added behavioral fact is the deprecation lifecycle status, which is genuinely useful and not in the annotations, but it says nothing about ordering, recency window, or what a returned run contains.

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?

It is very short with no filler, so nothing is wasted. However, the nested parentheses "(deprecated (use ...))" read as malformed and bury the migration note instead of front-loading it.

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 deprecated list tool with no output schema, the description leaves key questions unanswered: what fields a run has, whether results are ordered by recency, and which concrete tool replaces it. The path-only replacement reference makes the migration instruction unusable as written.

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 the single limit parameter is documented inline with its default and cap (<= 50, default 20). The description adds no meaning beyond the schema, which is acceptable at this coverage level but earns only the baseline.

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?

"Recent runs" names the resource and implies a recency-scoped listing, but no verb states whether it lists, fetches, or summarizes, and it never distinguishes itself from siblings such as analysis_quick_list or list_live_sessions. The deprecation note consumes most of the text without clarifying what a "run" is.

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?

It does tell the agent it is deprecated and points at a replacement, which is at least directional guidance. But the replacement is given as an HTTP path (/v1/analysis/quick) rather than a callable tool name, so an agent cannot act on it without guessing which sibling corresponds to that route.

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