force_reindex_search

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

No annotations are provided. The description only states 'force a full reindex' without disclosing any behavioral traits such as impact on system performance, required permissions, or side effects like clearing caches or invalidating other data.

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 short sentence, which is concise but at the expense of necessary detail. It fits the tool's purpose but could be more informative without being overly verbose.

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 complexity of a full reindex operation and the lack of annotations and output schema, the description is severely incomplete. It does not explain what happens during reindexing, the return value, or any implications for the system.

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 one parameter 'input' of type object with no properties, and the description provides no explanation of this parameter. With 0% schema coverage, the description completely fails to add meaning beyond the 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 verb 'force a full reindex' and the resource 'search index in Metabase'. It distinguishes from sibling tools like 'search' and 'reinit_search' by specifying 'full reindex', but does not explicitly differentiate from 'reinit_search'.

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 provided on when to use this tool versus alternatives like 'reinit_search', nor any prerequisites or conditions for use. The description lacks context on appropriate usage scenarios.

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