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

Goes well beyond the annotations: it discloses that the call is FREE/no credits, makes NO call to Google (reads MisarSEO's own Postgres), and critically that Google only retains ~8-10 trailing days of hourly data so an earlier startDate returns nothing. Annotations only cover read-only/idempotent/closed-world; the description adds the operational and data-window behavior.

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?

Front-loads the purpose and then layers the cost/behavioral caveats. Dense but every sentence carries distinct information (free, no Google call, data window, hour timezone). Slightly long, but nothing is filler.

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?

With rich annotations and full schema coverage and no output schema, the description covers the remaining gaps an agent needs: the data availability window, the cost profile, the upstream source, and the row field semantics. Nothing essential is missing.

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 coverage is 100%, so baseline is 3, but the description adds real meaning to startDate: a wider date range does not yield more history and an earlier startDate silently returns nothing. It also documents the `hour` field's 0-23 semantics in America/Los_Angeles, which is not in the schema at all.

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?

States a specific verb+resource (hourly Search Console totals for the connected property) and explicitly frames itself as the hourly counterpart to get_search_console_performance's daily archive. An agent can distinguish it from the sibling without opening either schema.

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?

Names the alternative (the daily archive get_search_console_performance) and clarifies the distinction (hourly vs daily) plus the 8-10 day window constraint. It gives clear context for when this is the right choice, though it stops short of an explicit 'use X instead when Y' conditional.

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