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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds only that results are paginated; it does not explain what happens when 'days' is null (the default), the ordering, or how the result set is bounded.

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 no filler, scope stated before the pagination note. It is efficient, though its brevity contributes to the under-specification noted elsewhere rather than being a virtue on its own.

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?

An output schema exists, so return values need no explanation. However, with 0% schema description coverage and a nullable default 'days', the description leaves a real gap around what time window is actually queried by default — the single most important thing an agent needs to call this correctly.

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 0%, so the description must carry the load for all three parameters. It vaguely gestures at 'days' and '(paginated)' but never states the semantics of a null 'days', the meaning of 'page', or the maximum/default of 'limit' (defaults only appear as bare schema values).

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 ('List') plus a precise resource ('most frequently detected web technologies') and scope ('over the last days', paginated). This cleanly separates it from per-scan siblings like get_technologies_by_scan and get_technology_stats, though it never names an alternative explicitly.

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?

No when-to-use statement, no exclusions, and no mention of the closely related search_technologies, get_technology_stats, or get_technology_combinations. An agent must infer from the phrase 'most frequently detected' that this is a global popularity ranking rather than a filtered search.

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