detect_quick_wins

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'detects' opportunities but doesn't explain what the output looks like (e.g., list of URLs with metrics, recommendations), whether it performs analysis or just filters data, or any limitations (e.g., data freshness, processing time). The description is too vague about the tool's actual behavior beyond the high-level purpose.

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 directly states the tool's purpose without unnecessary words. It's appropriately sized for a tool with a clear, focused function and doesn't waste space repeating information available in the schema. The structure is front-loaded with the core functionality.

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?

For a tool with 9 parameters, no annotations, and no output schema, the description is inadequate. It doesn't explain what constitutes a 'quick win' (beyond what parameters imply), what format the results take, or how the detection algorithm works. The agent must rely entirely on the parameter schema to understand the tool's operation, which is insufficient for proper tool selection and invocation.

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 100% description coverage, providing clear documentation for all 9 parameters including defaults and examples. The description adds no parameter-specific information beyond what's already in the schema. According to scoring rules, when schema_description_coverage is high (>80%), the baseline is 3 even with no param info in the description, which applies here.

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 tool's purpose as 'Automatically detect SEO quick wins and optimization opportunities' which specifies the action (detect) and target domain (SEO opportunities). It distinguishes itself from sibling tools like 'search_analytics' or 'enhanced_search_analytics' by focusing specifically on 'quick wins' rather than general analytics. However, it doesn't explicitly differentiate from all siblings (e.g., 'index_inspect' might also find optimization opportunities).

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. There's no mention of prerequisites (e.g., requiring Search Console data access), when this tool is preferred over 'search_analytics' or 'enhanced_search_analytics', or any exclusions (e.g., not for technical SEO audits). The agent must infer usage from the tool name and parameters alone.

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