Rebuild the search index

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

Beyond the bare idempotentHint=false annotation, the description discloses important runtime behavior: the reindex affects every page, the alternative is silent failure, and a confirmation token is required. This is far more transparent than most tool descriptions.

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?

Three sentences, each earning its place: what it does, when it is needed, and what it does on the basic engine. The most important information is front-loaded.

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 single-parameter tool with fully documented schema and no output schema, this description covers purpose, timing, side effects, and the odd failure mode. Nothing an agent needs to decide whether to call this tool is missing.

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 schema already fully documents confirm_token with a pattern and explanation. The description mentions the token requirement but adds no meaning beyond the schema. With 100% schema coverage, the baseline of 3 is appropriate.

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 states a specific verb and resource: 'Reindexes every page in the active search engine.' It also clarifies the exact trigger condition and scope, making it easy for an agent to distinguish this from unrelated sibling tools.

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 explicitly says when this is required ('after switching away from Database - Basic'), warns that the new engine 'starts empty' and 'silently returns nothing' otherwise, and notes that it does nothing on the basic engine. This gives clear go/no-go guidance.

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