get_search_analytics

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

With no annotations, the description carries full responsibility for behavioral disclosure. It does not mention auth requirements, rate limits, data freshness, or whether the operation is read-only. The minimal description fails to provide critical context.

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, clear sentence with no wasted words. It is appropriately front-loaded. However, for a tool with three optional parameters, slightly more detail might be warranted, but it remains concise.

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?

Without an output schema, the description should explain what metrics are returned (e.g., search volume, latency). It does not cover how time_range or include_performance affect the output. Given no annotations and no output schema, the description is incomplete.

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 includes descriptions for all three parameters (100% coverage). The description adds no additional meaning beyond 'analytics about search patterns and performance'. A score of 3 is appropriate because the description does not need to re-document the schema but also fails to explain how parameters influence results.

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 retrieves analytics about search patterns and performance. The verb 'get' and resource 'analytics' are specific, and the focus on search distinguishes it from sibling analytics tools like get_automation_analytics or get_project_analytics.

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 get_automation_analytics or get_project_insights. There is no mention of prerequisites, context, or exclusions.

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