list_pages_for_keyword

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

No annotations are present, and the description does not disclose whether the tool is read-only, destructive, or requires authentication. It fails to mention any behavioral traits such as rate limits or data volatility.

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 brief (one short sentence), but it sacrifices clarity for brevity. It could be improved by adding a verb and proper input/output hints while remaining concise.

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 lack of annotations, output schema, and parameter definitions, the description is insufficient. It does not explain what the tool returns or how it relates to other sibling tools, making it hard for an agent to use 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?

The input schema has no defined parameters (empty object with additionalProperties: true). The description does not clarify what input is expected (e.g., a keyword query parameter), leaving the agent to guess how to invoke the tool.

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 'Pages earning a query's clicks (cannibalization / canonical finding)' hints at the tool's purpose but is not a clear statement. It uses the verb 'earning' instead of 'list', and the parenthetical adds context but doesn't fully clarify what the tool does. More precise language would help.

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 like 'list_keywords_for_page' or other listing tools. The description does not mention any prerequisites, exclusions, or conditions for use.

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