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

The description adds important operational constraints beyond the `readOnlyHint: true` in annotations, such as requiring an API key. It also clarifies the scope of data returned (30-day daily breakdown), providing practical behavioral context.

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 definition is highly concise and efficient. Every phrase—data points, scope, and requirement—is essential and positioned at the front of the description.

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?

Given that there is no output schema, the description serves as the complete contract for the data the agent will receive (view count, last viewed time, 30-day breakdown), fully describing the function's result.

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 only one required parameter, `page_id`. Since schema description coverage is 0%, and the description does not provide any semantic information about what the `page_id` represents or how it should be formatted beyond what is in the schema, it meets the baseline score of 3.

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 clearly identifies the resource (page) and the action (view stats), specifically listing the data returned (count, time, breakdown). It is highly distinguishable from siblings like list_pages or update_page.

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 specifies a critical usage constraint: the page must belong to the user ('a page you own'). This limits the agent's ability to call the tool based on ownership rather than just existence, helping the agent decide if the tool is applicable.

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