Identify Quick Wins

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

With no annotations, the description carries the burden of explaining behavior. It discloses the core filtering logic, including the 'no indexing issues' condition, but does not explicitly state that this is a read-only analysis, how results are ordered, or whether any data is modified.

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, efficient sentence that front-loads the action and all key criteria. There is no filler or redundant restatement of the title.

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?

An output schema exists, so return value details are not required. Still, with seven parameters and no annotations, the description omits important operational context such as date-range semantics, site_url format, and how this tool differs from similar sibling reports.

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 low at 43%, so the description must compensate. It maps well to key parameters: 'high impressions' to min_impressions, 'low CTR' to max_ctr_pct, and 'ranked 4-10' to position_low/position_high. However, it says nothing about the required start_date and end_date parameters or the meaning of the date window.

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 and resource: 'Find pages worth quick optimization,' and gives specific selection criteria (high impressions, low CTR, ranked 4-10, no indexing issues). These criteria differentiate it from the general sibling analytics tools, though it does not explicitly name a sibling it is not.

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 criteria imply when to use the tool: for pages in positions 4-10 with high impressions and low CTR. However, it does not state when not to use it or which alternative, such as get_ctr_optimization_report or get_position_band_report, would be more appropriate.

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