Sync to Spotlight

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

Annotations indicate idempotency and non-destructive behavior, which the description does not elaborate. The description adds little beyond the purpose; it does not disclose side effects, permission requirements, or impact on existing Spotlight data.

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 very concise and front-loaded, with a single sentence that clearly states the action. However, it is truncated, which slightly reduces clarity. Overall, it effectively conveys the core purpose with minimal waste.

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 the tool interacts with macOS Core Spotlight and has no output schema, the description should explain prerequisites (e.g., data must be indexed first), behavior on multiple runs, and what makes data discoverable. The current description is incomplete for understanding the full context of usage.

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?

There are no parameters in the input schema, so schema coverage is 100%. According to guidelines, baseline score is 4 for zero parameters. The description adds no parameter-related information, but no additional semantics are needed.

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 the action 'push semantically indexed data to macOS Core Spotlight' and the destination, making the purpose clear. It does not explicitly differentiate from sibling tools like 'semantic_index' or 'spotlight_clear', but the verb 'sync' and mention of Spotlight imply a distinct 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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., need to run semantic_index first) or scenarios where this tool is appropriate.

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