Rebuild Vector Index

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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false; the description's main addition is the admin-scope requirement, which is genuinely valuable. It does not disclose whether the existing index is dropped first (relevant given destructiveHint=false and idempotentHint=false), how long the rebuild takes, or whether it is blocking.

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?

One sentence with the access requirement front-loaded in brackets; no filler. It is arguably over-compressed given the unknowns it leaves, but structurally sound.

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 the admin prerequisite is covered. For a whole-index mutation with two undocumented parameters and no cost or scope-of-impact statement, the description is only minimally sufficient.

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% and neither parameter is documented anywhere. The description says 'all existing entries' without clarifying how project_number scopes the rebuild or what use_test_db does, so an agent cannot tell whether omitting project_number rebuilds every project.

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?

States a specific verb (Rebuild) and resource (semantic search vector index) plus the source of data ('all existing entries'), which implicitly separates it from add_to_vector_index (incremental) and get_vector_index_stats (read-only). It does not name those siblings explicitly, so an agent must infer the contrast.

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 '[REQUIRES ADMIN SCOPE]' prefix gives a concrete prerequisite, which is useful. However there is no statement of when to prefer a full rebuild over add_to_vector_index, nor any warning about cost/downtime or whether existing vectors are replaced.

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