fulltextsearch_index

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions the rebuild action and the wipe behavior of reset, but omits important details such as whether the operation is long-running, requires maintenance mode, locks resources, or requires specific permissions. This is minimal disclosure.

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 extremely concise, consisting of two sentences with no wasted words. The first sentence clearly states the core function, and the second sentence adds the optional behavior. This is perfectly front-loaded and efficient.

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 that an output schema exists, the description need not explain return values. However, the tool's description lacks context about the scope of reindexing (all content?), potential impact on system performance, and prerequisites. It is adequate but not thorough for a potentially impactful administrative tool.

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 0%, so the description must compensate. For the single parameter 'reset', the description explains its purpose ('wipe the index before reindexing'), adding significant value beyond the schema's type-only definition. No other parameters exist.

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 rebuilds the full-text search index, specifying the underlying technology (OpenSearch). The verb 'Rebuild' combined with the resource 'full-text search index' is specific and distinct from any sibling tools, none of which relate to search indexing.

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 gives a brief usage note for the reset parameter but does not provide explicit guidance on when to use the tool (e.g., after configuration changes, index corruption). Since there are no sibling search tools, the usage context is implied but not fully articulated.

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