urlscan_get_result

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

No annotations are provided, so the description must fully convey behavioral traits. It only states 'Get the result,' implying a read operation, but fails to disclose whether authentication (api_key) is required, rate limits, or error handling (e.g., invalid UUID). The minimal description leaves significant behavioral uncertainty.

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?

The description is a single, concise sentence that gets directly to the point. It avoids unnecessary words and is appropriately front-loaded. However, it could be slightly more structured to include parameter hints without sacrificing conciseness.

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?

The tool has no output schema, so the description should cover what the result contains or its format. It does not mention the structure of the response (e.g., JSON fields, status). For a tool that returns data, this leaves an agent with insufficient context to handle the output.

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?

With 0% schema description coverage, the description should compensate by explaining parameters. It mentions 'by UUID' which clarifies the uuid parameter, but it does not explain the api_key parameter (purpose, optionality, or where to obtain it). The description adds very little beyond the schema itself.

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 clearly states the tool's purpose: 'Get the result of a urlscan.io scan by UUID.' It uses a specific verb ('Get') and resource ('result of a urlscan.io scan'), effectively distinguishing it from sibling tools like urlscan_scan (which initiates a scan) and urlscan_search (which searches scans).

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 usage when a scan UUID is available, but it lacks explicit guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., needing to have performed a scan first) or when not to use it. While the purpose is clear, an agent would benefit from more explicit context.

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