Get HitKeep AI Visibility

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

Annotations already specify readOnlyHint=true and openWorldHint=false. The description adds what data is returned (overview, timeseries, correlation) but no side-effect or requirement details. It doesn't contradict annotations, and the added behavioral detail is useful but modest.

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?

Single sentence, front-loaded with the action ('Read') and immediately states the resource and scope. No wasted words or redundancies.

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 has many optional filters, but the schema covers all parameters (100% coverage). The output schema exists for return data. The description adequately conveys the core function (overview, timeseries, correlation) without needing to enumerate filters. It's complete for a read operation with rich schema documentation.

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% with detailed parameter descriptions spancho each parameter. The description adds minimal value beyond saying 'for one site' and mentioning correlation, which maps to a parameter. Baseline 3 applies since schema already covers all parameters.

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 AI crawler fetch overview, timeseries, and optional correlation for a single site. 'Read' is a specific verb, and the resource is the site's AI visibility data. It also distinguishes itself from siblings like get_site_overview and get_search_console by specifying 'AI crawler'.

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 use when you need AI crawler visibility data for a site, but it does not explicitly mention when not to use it or alternative tools. However, the tool name and sibling context make the purpose clear, so it's adequate but lacking explicit exclusions.

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