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

Annotations only supply readOnlyHint=false and openWorldHint=true, and the description adds genuinely useful traits: a fixed bounded plan, observation timestamps preserved on source/image facts, and disclosure of missing evidence. However, it never clarifies why a screenshot tool is flagged non-read-only, nor mentions cost, latency, auth, or what state a bounded plan touches.

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 sentences of moderate length, but the opening sentence duplicates the tool name and relies on abstract phrasing ('explicit observation scope', 'fixed bounded plan') that is not immediately actionable. The limitation caveat does earn its place.

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?

With no output schema and no parameter descriptions, the description should explain what comes back (image URLs? coverage report?) and what task_id does. It instead only states interpretation limits, leaving an agent unable to predict the result shape or the calling sequence for this open-world tool.

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?

The single parameter task_id has 0% schema description coverage and the description never mentions it — no explanation of what a task_id is, where it comes from, or whether it starts or references a job. Since the parameter is undocumented in both structured data and prose, the description fails to compensate.

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 name and first sentence both say 'Serp screenshot evidence', so the description largely restates the title rather than stating a concrete verb + resource. The added clauses ('explicit observation scope and missing evidence', 'fixed bounded plan') hint that it returns screenshot evidence plus coverage metadata, but an agent cannot confidently distinguish it from siblings like nexscope_page_screenshot or nexscope_seo_page_evidence.

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?

There is no statement of when to use this tool, when not to, or which sibling to prefer for a page screenshot vs. SERP evidence. The closing caveat ('a screenshot does not prove current indexing or complete website coverage') is an interpretation warning, not usage selection guidance.

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