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

The description details specific access behaviors (Founder's browser SCons vs. Shipfound's stored key), which is highly valuable. However, it contradicts the provided `readOnlyHint: false` annotation, as this is fundamentally a read/retrieval operation, causing a major inconsistency in tool behavior 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?

While effective, the description is overly verbose. The necessity of explaining the complex data acquisition methods (browser sessions vs. stored keys) bloats the structure, sacrificing conciseness for necessary operational context.

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?

It is highly complete regarding the mechanics of the read operation. Even without an output schema, the description explains exactly what is being pulled and where the data comes from, providing sufficient context for an agent to execute the function correctly.

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?

Given the 50% schema description coverage, the description adds substantial semantic value by explaining that `rows` and `prev` represent two different time windows and data sources (Search Console performance metrics vs. historical clicks/impressions). This bridges the gap left by the sparse 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 purpose is extremely clear: to read and compare site search data across Google and Bing. It precisely defines the metrics and the comparison logic (28 days against the preceding 28 days), distinguishing itself from sibling tools like `seo_set`.

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?

It clearly indicates the specific performance metrics (clicks, impressions, CTR, position) and the scope (Google and Bing). It guides the user on the comparison timeframe, making it easy to know *when* to invoke it for performance review.

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