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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely says searches are 'shown for' a page; it does not disclose read-only behavior, aggregation, pagination, default date windows, or data-availability caveats. For a query-style tool this is thin.

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 short and free of filler, but brevity comes at the cost of clarity and grammar. 'What searches a specific page is shown for' is confusingly worded and under-specified; it is not effective concise communication.

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 7 parameters, no annotations, no output schema, and overlapping sibling tools, a one-clause description is far from complete. It does not describe returned rows, metric fields, default behavior, pagination, or selection criteria, leaving too much for the agent to infer.

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 the parameters are already well documented in the schema. The tool description adds no additional parameter meaning: it does not explain how `page`, `match`, `days`, or `end_date` interact beyond what the schema states.

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 'What searches a specific page is shown for' is ungrammatical and lacks an explicit verb like get, list, or return. It gestures at page-level query data but does not clearly say what the tool returns (e.g., query strings, metrics, rankings), and it does not distinguish itself from siblings like `query` or `inspect_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?

There is no guidance on when to use this tool versus alternatives such as `query`, `top`, or `inspect_url`. No context, exclusions, or alternative conditions are provided; an agent can only infer that it might be useful when focusing on a single page.

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