Get HitKeep Site Overview

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

The description confirms the read-only nature matching annotations, and adds details about the data returned (KPIs, dimensions, goals, chart data, optional comparison). This adds useful context beyond the readOnlyHint annotation.

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 concise sentence that efficiently conveys the tool's purpose without any unnecessary words.

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 presence of a comprehensive input schema, output schema, and readOnlyHint annotation, the description adequately covers the tool's function. Could mention that it returns multiple data types, but it's sufficient.

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 has 100% description coverage for all 6 parameters. The description mentions 'optional comparison' which aligns with compare parameters, but does not add significant meaning beyond the schema.

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', the specific resource 'aggregate traffic KPIs, top dimensions, goals, chart data', and scope 'for one site'. It is distinct from sibling tools like hitkeep_get_ecommerce or hitkeep_get_search_console.

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 per-site usage but does not provide explicit guidance on when to choose this tool over siblings. No 'when not to use' or alternative tool references are given.

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