get_top_queries

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

No annotations are provided, so the description must carry the full burden. It does not disclose any behavioral traits such as whether the tool is read-only, any rate limits, pagination details, or data freshness. The minimal description leaves the agent without critical safety or performance information.

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 sentence, which is concise but overly terse. It lacks structure and omits important details about parameters and usage. Better to front-load key information and provide more substance in a few sentences.

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?

Despite having an output schema, the description does not cover the purpose of the numerous parameters (8 total, 2 required). It fails to provide context for the 'filters' or 'data_state' fields, making the tool hard to use correctly without external knowledge.

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 0%, and the description does not add any meaning beyond the parameter titles. It fails to explain what each parameter does, including 'site_url', 'search_type', 'data_state', and 'filters'. The agent would rely solely on parameter titles, which are insufficient for complex optional fields.

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 identifies the action ('Get'), resource ('top query rows'), and context ('for a property over a date range'). It distinguishes from siblings like 'get_top_pages' by specifying 'queries' instead of 'pages'. However, it could be more precise about the 'property' parameter (likely 'site_url').

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?

The description provides no guidance on when to use this tool versus alternatives like 'get_top_pages' or 'get_dimension_breakdown'. It lacks context about what scenarios it is best suited for or when not to use it.

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