reindexar

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

Annotations already establish this is a non-read-only, non-destructive, closed-world operation. The description adds useful context that indexing normally happens automatically every minute, explaining why a manual trigger exists, but says nothing about runtime, blocking behavior, or whether an in-progress index is replaced.

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?

A single front-loaded sentence with the action first and the qualifying context in parentheses. Nothing is wasted and no sentence is extraneous.

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 values need no explanation, and there are no parameters to document. What remains missing is behavioral detail about how long the reindex takes or whether the call blocks, which would help an agent decide to invoke it.

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 tool takes no parameters (0 params, schema coverage 100%), so the baseline is 4. There is nothing parameter-related that the description could reasonably clarify.

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 ("Força uma atualização do índice agora"), making the action unambiguous. It does not differentiate itself from any sibling tool, though the reindex operation is naturally distinct from the read/write tools in the list.

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 parenthetical "normalmente é automático a cada minuto" implies this manual trigger is only needed when immediate indexing is required, which is implicit usage guidance. It never explicitly states when to call this instead of relying on the automatic cycle, nor any exclusions.

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