Clear Spotlight Index

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's statement 'without clearing the local vec...' adds some context by clarifying that the local vector store is preserved. However, the truncation undermines this, and no other behaviors (e.g., permissions, re-indexing) are disclosed.

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, which is concise in length, but it appears truncated, making it incomplete and reducing effectiveness. A complete sentence would be better.

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 no output schema and a simple parameterless call, the description still leaves gaps: it does not explain what happens after removal (e.g., whether re-indexing is automatic), any prerequisites, or potential side effects on Spotlight functionality.

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 input schema has no parameters, and schema coverage is 100%. The description does not need to add parameter details; it correctly implies no configuration is 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 'Remove all AirMCP entries from macOS Spotlight', which clearly identifies the action and resource. However, the truncation at 'without clearing the local vec...' leaves ambiguity about the scope, and it does not fully distinguish from siblings like semantic_clear (which likely clears the semantic index) or spotlight_sync.

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 such as semantic_clear or spotlight_sync. An AI agent would have to infer usage from the name and title alone.

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