Get HitKeep Web Vitals

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

The description adds context beyond the readOnlyHint annotation by specifying the exact data returned (p75, sample counts, rating counts) and the availability of page or visitor-context breakdowns. It accurately reflects a read-only, idempotent operation without contradicting annotations.

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 a single, front-loaded sentence that efficiently conveys the tool's purpose and scope. Every word adds value, with no redundant content.

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?

With an output schema available and fully described parameters, the description sufficiently covers the main functionality. It outlines the key data types (p75, counts) and optional breakdowns, and while it could mention timing defaults, these are in the schema. The description is adequate for the tool's complexity.

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 already provides complete descriptions for all 10 parameters (coverage 100%). The tool description mentions 'page or visitor-context breakdowns' but does not add substantial semantic detail beyond what the schema offers. Baseline of 3 is appropriate given full schema coverage.

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 states the tool reads aggregate Web Vitals (p75, sample counts, rating counts) for one site, with optional breakdowns. The verb 'read' and specific resource distinguish it from sibling tools like site_overview or event_breakdown.

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 guidance is provided on when to use this tool versus alternatives such as hitkeep_get_site_overview or hitkeep_get_event_breakdown. The description does not mention exclusions or scenarios where other tools would be more appropriate.

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