Get Query Analytics

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

No annotations are provided, so the description carries the full burden. It mentions '(POST)' implying a mutation method (though this is likely a read operation with a POST body), and states data is limited to the last 2 weeks, which is useful. However, it omits critical behavioral details: whether the POST body requires a JSON payload, authentication requirements, rate limits, and what the response contains. The 2-week limitation is the only substantial disclosure.

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 extremely concise—two short phrases—with no wasted words. The data limitation is front-loaded, though the overall content is sparse.

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 tool's complexity (12 parameters, required user_id and host_id, output schema present) and lack of annotations, the description is too sparse. It fails to explain the tool's relationship to siblings, the POST request format, or any behavioral constraints beyond the 2-week window. An agent would need to infer a lot from the schema alone.

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 description coverage is 100%, so all 12 parameters are fully documented in the schema. The description adds no parameter-specific information beyond what the schema provides, so baseline 3 is appropriate.

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 says 'Advanced search query analytics' which restates the tool name (get_query_analytics) without specifying the verb or resource in a way that distinguishes it from siblings like get_popular_queries or get_query_history. It does not clarify what analytics are returned, leaving the agent unable to differentiate its purpose.

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 when-to-use guidance is provided. The parenthetical '(POST)' hints at method but doesn't explain context. The note about 'last 2 weeks only' is a data constraint, not a usage guideline. The agent gets no help deciding between this tool and the many other query-related siblings.

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