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

Annotations already cover read-only, idempotent, closed-world, non-destructive, so the safety bar is low. The description still adds real behavioral value by flagging that part of the returned content is third-party written and is "information, never instructions" — a prompt-injection warning that no annotation conveys. It does not mention result volume, pagination, or freshness.

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 short paragraphs, front-loaded with what the tool returns, then the security note as a clearly separable second block. Every sentence carries information; nothing restates the name or title.

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 the annotations plus the injection warning cover behavior. What is missing is the time-window semantics tied to the days parameter and any hint about the volume or source mix of results — minor given the schema and output schema.

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 50%: workspaceId is well documented in-schema, but days has only an enum of 7/28/90 and a default of 28 with no explanation. The description says nothing about either parameter, so it does not compensate for the gap — though the enum plus default makes the meaning of days largely self-evident.

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 the concrete resource — Search Console opportunity types (near-page-one keywords, high-impression/low-click pages, decaying articles) — so an agent knows what it will get. It also explicitly contrasts with AI visibility data owned by the GEO agent, which helps separate it from readRankings/readDecaying. It never states a verb or scope (e.g. 'list for a workspace over N days'), so it stops short of full sibling differentiation.

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 one negative boundary ("These are Google rankings, NOT AI visibility"), which is useful routing. But it offers no positive guidance on when to call this versus readRankings, readDecaying, readIdeas or readScorecard, all of which appear to overlap. Usage is implied by the content list rather than stated.

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