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

Annotations already establish read-only, idempotent, non-destructive, non-open-world behavior, so the bar is lowered. The description still adds real context: result ordering, that both listing and rank fetches appear here, the failure-vs-absent-position distinction, and a concrete authentication prerequisite with login commands.

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?

Three short blocks, front-loaded with what the tool returns before the usage hint and the auth note. Sentence count is defensible; the auth paragraph is somewhat mechanical but operationally necessary.

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?

No output schema exists, and the description compensates by naming the returned fields (outcome, error) and ordering. Auth requirements and the dual fetch-type coverage are disclosed. A brief note on default result volume or pagination would close the remaining gap for a list tool with a limit parameter.

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 coverage is 67%, with limit (default 20), status (three-value enum) and extension_id documented in the schema itself. The description adds no parameter-level meaning — not even which filters are combinable or how status interacts with the run types it describes — so this sits at the baseline for partial coverage.

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+resource ('recent scrape attempts against your own extensions') with ordering ('newest first') and return content ('outcome and any error'). It also scopes what a run covers (listing fetches and rank fetches), which separates it from get_keyword_ranks in the sibling set.

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 an explicit trigger: 'Use this after add_keyword to watch the rank fetch,' and explains the payoff (a failed fetch surfaces as a failure instead of a missing position). It does not name a competing tool the agent should prefer in other situations, so it stops short of full when/when-not guidance.

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