Reconcile Sharing Indexes

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so the description does not need to restate these. It adds the scope 'all sharing indexes' but does not explain side effects, runtime expectations, or whether it is safe to run concurrently. The description adds some value beyond annotations but lacks depth.

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 sentence of 9 words, front-loaded with the action ('Trigger') and object. It contains no filler and every word contributes to meaning.

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?

For a zero-parameter, no-output-schema trigger tool, the description is adequately complete. It states the action and scope. However, it could briefly mention intended use (e.g., 'run periodically to fix inconsistencies') or expected outcome to fully contextualize the tool for an agent.

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 has zero parameters and schema coverage is 100% (empty schema). Baseline for zero-parameter tools is 4. The description does not need to add parameter semantics, and none is provided.

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 uses the specific verb 'trigger' and clearly identifies the resource ('all sharing indexes') and the action ('reconciliation pass'). It distinguishes from sibling sharing tools (e.g., lyzr_sharing_check_access, lyzr_sharing_list_groups) by focusing on an internal maintenance operation.

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 context is clear: this is a maintenance operation for reconciling sharing indexes. However, it does not explicitly state when to use it vs. alternatives or mention any prerequisites or exclusions. For a zero-parameter trigger tool, the implied usage is adequate but not explicit.

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