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

Annotations provide destructiveHint=true and readOnlyHint=false, but the description adds the concrete consequence of consuming 1-3 CalmSEO credits depending on depth. This is valuable beyond the structured hints, as it warns the agent about a resource cost. It does not elaborate on the destructive hint, but the credit consumption is a meaningful disclosure in itself, so the bar is met.

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, zero filler. The core action and resource are front-loaded, followed by a concise note on what it returns and the credit cost. Every word earns its place; no restructuring would improve 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 6-parameter tool with no output schema, the description is minimal. It states the return type ('compact ranking results') but does not hint at the result fields or any pagination/error behavior. The main parameters are covered by the schema, but the overall context for an agent deciding how to interpret the response is thin. Adequate but not comprehensive.

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% (4 of 6 parameters have descriptions). The description mentions keyword, location, language, and depth, which aligns with the schema, but it does not provide additional semantics for the two uncovered parameters (device, search_engine). The phrase 'Google or Bing' does hint at search_engine, but not enough to fully compensate for the missing schema descriptions. This sits at the baseline for moderate 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?

The description opens with 'Live Google or Bing organic SERP search', a specific verb and resource, and goes on to say it returns compact ranking results. This clearly distinguishes it from sibling tools like get_gsc_top_queries or find_keyword_ideas, which focus on analytics or keyword suggestions. No ambiguity remains about what the tool does.

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?

The description implies real-time use ('Live') and names the supported engines, but gives no explicit guidance on when to choose this tool over alternatives. It does not mention any exclusions or point to siblings, so the agent must infer the context from the stated behavior. This is adequate but not explicit.

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