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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds useful behavioral detail about the lookback window ('last 7 days') and per-AI breakdown. It says nothing about result size, pagination, or what happens with zero sites, which is the remaining gap.

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?

It uses two sentences: the first front-loads the scope and enumerates the returned fields, and the second explains why to call it. The field enumeration is dense and slightly run-on, but every clause carries information.

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?

Because the output schema is present, the description need not restate return shapes, and it does explain the temporal scope of the data. It omits edge-case behavior, such as an empty site list or any account prerequisites, which keeps it a point below full completeness.

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?

This tool takes zero parameters, so the baseline of 4 applies, and the schema needs no compensation. The description correctly presents a parameterless call.

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 names a specific action and resource ('Every site the person watches in aipozi') and lists the returned data: id, plan, market, last check time, mention counts per AI engine with address, DR, and a 7-day window. A reader can distinguish this tool from siblings such as rivals or domain_rating without opening a schema.

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 explicit use cases ('see which sites exist, or get a site id for another tool'), which is clear context. It does not name exclusions or say when to prefer a sibling tool instead, so it falls short of a 5.

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