analytics_search_appearance

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

No annotations provided; description carries full burden. It discloses it is a read operation ('Get') but does not mention side effects, data freshness, rate limits, or authentication needs. The minimal description leaves behavioral traits unclear.

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 conveys the essential purpose and time range. No unnecessary words, and the structure is front-loaded with the action and resource.

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 no output schema and 4 parameters, the description is adequate but lacks detail on what 'search appearance type' means or what the output structure looks like. The agent may need to infer response fields. More details on appearance types and output would improve completeness.

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 description adds no additional meaning beyond the schema. Each parameter (days, limit, sortBy, siteUrl) is already described in the schema. The description does not provide extra context or constraints.

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 a performance breakdown by search appearance type for a specified period, using specific verb 'Get' and resource 'performance breakdown by search appearance type'. It distinguishes from sibling tools like analytics_top_queries or analytics_top_pages which focus on different dimensions.

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 explicit guidance on when to use this tool versus alternatives. While the description implies usage for appearance-type breakdowns, it lacks context on when to prefer it over other analytics tools or any exclusions. The agent must infer from the tool name alone.

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