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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the state precondition (job must be completed) and the content categories returned, but says nothing about behavior for an incomplete/invalid crawl_id or whether results are partial. With annotations carrying the safety load, this is adequate but thin.

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?

A single front-loaded sentence with the verb and resource first and the return contents second. No filler, no repetition of the 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?

There is no output schema, so the description must convey return values, and it does name the three main artifacts (scripts, test cases, flow memory). It leaves the shape of the response (structure, sizes, pagination) and failure modes unspecified, which is a modest gap for a read 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?

Schema description coverage is 100%, with crawl_id and the analytics-only context parameter fully documented in the schema, so the baseline of 3 applies. The description adds no meaning beyond the schema, such as the format of the crawl ID or where to obtain it.

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 a specific verb (get) and resource (AI crawl results) and enumerates the payload: test scripts, test cases, flow memory. It does not distinguish itself from close siblings like check_ai_crawl_status or list_ai_crawl_jobs, so an agent must infer the boundary from those tools' own descriptions.

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 adjective 'completed' implies results should be fetched only after the job finishes, which weakly points to check_ai_crawl_status as the prerequisite. However, no alternative is named and there is no explicit when-not guidance (e.g., what to do for a job still running, or how this differs from list_ai_crawl_jobs).

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