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

Annotations already declare readOnly, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds the sort order, which is real behavioral value, but says nothing about the truncation quirk or result volume that the schema hints at.

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, no filler, with the result set and ordering front-loaded before the usage hint. Nothing is redundant or buried.

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?

An output schema exists, so return values need not be explained, and annotations cover safety. The definition is adequate for a two-parameter read tool, though it omits any mention of workspace scoping behavior that a caller in a multi-workspace connection would benefit from.

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 baseline is 3; the description contributes no additional meaning about limit or workspaceId beyond what the schema already states, including the unusual 'no more than five are ever found' cap.

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 the specific resource (published articles) and the exact signal (falling search clicks) plus an ordering ('worst first'), which is more than the title alone conveys. It is distinguishable from ranking/performance siblings by the 'decaying' framing, but it never names those siblings to draw the line explicitly.

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 decide what to refresh before writing anything new' gives a decision context, but offers no explicit when-not-to-use guidance and never names an alternative such as readPerformance or readRankings for healthy-traffic lookups.

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