webmaster_get_query_history

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

The description explicitly says 'Read', indicating a non-destructive operation. Since no annotations are provided, this direct statement about read-only behavior is transparent. However, it does not disclose any side effects (which are unlikely) or other behavioral details.

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?

A single, concise sentence that efficiently conveys the tool's purpose without redundancy or extraneous information.

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 the moderate complexity with 6 parameters and an output schema, the description is minimal. It lacks essential details such as date format, expected behavior for null values, default indicators, or any specifics about the response format. The tool name is not explicitly mentioned in the description, though it is implied.

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 description only adds a hint about '31 days' (likely a date range constraint) and 'aggregate or selected-query indicators', which partially relates to query_indicator and device_type_indicator. It does not explain the date format, the meaning of each indicator, or the role of host_id, leaving most parameters undefined beyond the 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 description clearly states the action ('Read'), the resource (query history), and the scope ('aggregate or selected-query indicators') with a time limit of 31 days. It is specific and distinguishable from sibling tools.

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. It does not mention any conditions, prerequisites, or comparative scenarios.

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