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

The annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds no new behavioral details beyond what the schema and annotations provide; it does not mention pagination, rate limits, or response format. It is consistent with annotations, so no contradiction.

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 consists of two nearly identical sentences, repeating the same information. This is redundant and wastes space; a single sentence would suffice. The duplication makes it less concise and poorly structured.

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 lacks any mention of its relationship to shop_list_page_views_per_weekday, which is a likely alternative for aggregated weekday data. It also does not clarify the output format (e.g., individual events vs. counts per day), which is ambiguous. Given the annotations cover safety, the main missing context is the differentiation and output nature, making it incomplete.

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?

The input schema provides complete descriptions for all three parameters, including formats, defaults, and the platform enum, giving 100% coverage. The description adds no additional parameter semantics or interaction details. With such high schema coverage, the baseline score of 3 is appropriate.

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 clear verb and resource: it returns the history of page views within a time range and platform. It is distinct from sibling shop_list_page_views_per_weekday by its name, but the description does not explicitly differentiate them. Overall the purpose is clear, though not as strong as it could be with an explicit alternative.

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?

There is no guidance on when to use this tool versus shop_list_page_views_per_weekday or other list tools. The description merely repeats the function without any usage context, exclusions, or alternative recommendations. This is a significant gap given the existence of a closely related sibling.

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