Sweep a phrase template across niches

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

No annotations are provided, so the description carries the full burden. It explains the mechanism (substituting niche into template, running outlier search per niche) and discloses the expensive nature. However, it does not mention if the tool is read-only or any side effects, and output format is unspecified.

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 concise with two clear paragraphs: one for purpose and one for cost. It front-loads the action but could be slightly more structured.

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?

With 8 parameters and no output schema, the description omits what the returned data looks like. It says 'rank the hits across all niches' but does not specify fields or format, leaving a significant gap.

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 baseline is 3. The description adds an example ('beginner mistakes {niche}') but does not provide additional meaning beyond the well-documented 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 tool's purpose: running an outlier search per niche by substituting a phrase template, ranking hits across niches. It answers a specific question and distinguishes from siblings like find_outliers.

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 warns about the high cost (percent of daily quota), implying it should be used sparingly and for cross-niche comparison. However, it doesn't explicitly state when not to use it or direct users to an alternative for single-niche searches.

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