Build Semantic Index

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, but the description adds no additional behavioral context beyond listing source apps. It does not disclose potential side effects like overwriting the existing index, time consumption, or permission requirements. Since the annotations carry the burden, the description fails to add value.

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 incomplete sentence (ends with '...'). It is short but lacks proper structure. It could be more concise or informative. It earns its place but is not exemplary in conciseness.

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 one optional parameter and no output schema, the description should explain the importance of indexing, its effect on other tools, and potential duration. It does not mention that indexing is needed for semantic search or that it may be destructive. The description is insufficient for an agent to fully understand the tool's role and impact.

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 100%, so the schema fully documents the 'sources' parameter with enum values. The description lists some apps (Notes, Calendar, etc.) but is incomplete (missing 'finder'). It adds marginal meaning by indicating the apps are 'enabled Apple apps' but largely repeats what the schema provides. Baseline 3 is appropriate.

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 'Index data from enabled Apple apps' which clearly indicates the tool builds a semantic index from specified apps. The title 'Build Semantic Index' reinforces the purpose. However, the description is truncated with '...' and could be more specific about the output or effect. It effectively distinguishes from siblings like semantic_search and semantic_clear.

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 description provides no guidance on when to use this tool versus alternatives such as semantic_search, scan_notes, or other indexing tools. It does not mention that indexing is a prerequisite for semantic search, nor does it explain when to re-index or that it may overwrite previous index. No explicit usage context is given.

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