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

Goes well beyond annotations (readOnlyHint=false, idempotentHint=true, openWorldHint=true) by disclosing that the scan is asynchronous ("runs in the background within a few minutes"), the throttle window, the throttled response payload (status/retry_after_seconds) and that it changes nothing, plus cost (0 credits). Failure modes site_scan_not_verified and site_scan_plan_required (403) are spelled out, which is exactly what an agent needs before mutating state.

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?

Four tight sentences, front-loaded with purpose then mechanics, throttle, and errors; nothing is filler. It is dense to the point of being error-code heavy, which slightly crowds the core instruction but every clause is actionable.

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 telling the agent where the result is read from (get_ai_visibility) and what a throttled call returns. For a one-parameter background job, nothing needed to invoke or interpret it correctly is missing.

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 site_id parameter is already documented in the schema including its source tools, so the description adds no parameter-level detail beyond restating "one verified RankParse website." Baseline 3 applies when the schema does the work.

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?

Specific verb+resource: "Queue a fresh AI visibility scan for one verified RankParse website," with the scope narrowed to a single verified site. It clearly distinguishes itself from the read-side sibling get_ai_visibility, which the description explicitly points to for results.

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 a concrete trigger ("after the user fixed robots.txt or published llms.txt"), names the alternative for retrieval (get_ai_visibility), and states the preconditions that gate a valid call: verified site, non-Free plan, and 10-minute throttle.

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