hac_solr_reindex

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

With no annotations, the description carries full burden. It usefully discloses that the build is in-process, immediate, and bypasses the cron queue, but says nothing about duration, blocking behavior, resource load, required permissions, or whether the operation is safe/idempotent.

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 no filler; the key action and its distinguishing benefit (bypassing cron delays) come first. Appropriately sized for a simple trigger tool.

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 needn't be explained, and the core action is covered. However, for a potentially heavy index-rebuild operation with zero annotation and parameter coverage, the description leaves meaningful gaps around mode semantics and side effects.

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 coverage is 0% and the description only mentions FULL/UPDATE modes in passing without explaining their difference, tradeoffs, or defaults. The config_name parameter is never addressed at all, so the description fails to compensate for the undocumented 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?

States a specific verb+resource: 'Triggers an immediate in-process Solr index build', and even names the modes (FULL/UPDATE). It is clearly distinct from hac_solr_status, though it doesn't explicitly differentiate from any sibling by name.

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?

Gives clear context for use: run it when you want to bypass cronjob queue delays and build immediately. No explicit 'when not to use' or named alternative is offered, but the intent is unambiguous.

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