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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds valuable behavioral context beyond that: auto-detection of several log formats, the per-line classification output, rollups, and the detail that lines whose address contradicts their claim are surfaced. This goes well beyond the annotation baseline.

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 dense but every sentence earns its place: input forms, output components, a hard constraint, and a concrete example. It is front-loaded with the core behavior and wastes no words.

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 carries the burden of explaining return values, and it does so reasonably well by naming per-line fields, rollup dimensions, contradiction detection, and a sample result. It does not describe exact response shapes or failure modes, but the core call behavior is adequately covered.

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 100%, so the baseline is 3. The description adds meaningful semantic information not in the schema: the accepted log formats (combined, JSON, uniq -c, IP+UA, bare UA), the 'log text, never a URL' constraint, and an example mapping a line to Googlebot/Google/search/verified. That clearly enriches the log parameter.

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 states a specific action and resource: paste log lines and get per-line crawler, operator, purpose, and blocking-cost analysis, plus rollups and contradiction detection. It is clearly not a generic API, but it does not explicitly distinguish itself from the sibling tools, so it stops short of a 5.

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?

It gives useful input guidance: accepted formats are auto-detected, and URLs are explicitly excluded. However, it never says when to prefer this tool over siblings like robots_from_log or summarize_by_operator; usage context is implied rather than stated.

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