Get HitKeep AI Visibility

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

Annotations already indicate readOnlyHint=true, so the description does not need to repeat safety. The description adds context about the data returned (overview, timeseries, correlation) but omits details like pagination, data limits, or authentication requirements. It adds some value beyond 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 sentence of 14 words, highly concise and front-loaded with the main purpose. It avoids unnecessary detail and is easy to parse, though it could benefit from a bit more structure.

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 the existence of an output schema (which documents return values) and well-documented parameters (100% coverage), the description provides adequate context by naming the three main components. For a read-only tool with rich schema and annotations, this is sufficiently complete.

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 coverage is 100%, so parameters are already documented. The description mentions 'optional fetch-to-visit correlation' which corresponds to include_correlation, but adds no new meaning beyond the schema descriptions. Baseline 3 applies.

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 verb 'Read' and specifies the resource as 'AI crawler fetch overview, timeseries, and optional fetch-to-visit correlation for one site'. It is specific and distinct from sibling tools like hitkeep_get_site_overview or hitkeep_get_ecommerce, which cover different subjects.

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?

The description implies when to use this tool (for AI crawler data) but does not explicitly state when not to use it or provide alternatives. There is no guidance on prerequisites or comparison with sibling tools.

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