Enable Semantic Search

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

The annotations only provide generic false hints, so the description carries the burden of explaining behavior. It discloses meaningful side effects and constraints: the engine enforces manage-semantic and creator authority, existing records are backfilled, allowed-model constraints apply, and the operation is scoped to one keyspace. This goes well beyond what annotations alone tell an agent.

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 focused and efficiently structured: a one-line purpose, a short paragraph of behavioral constraints, and a clear Args list. Every sentence adds necessary information without fluff or redundancy.

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?

The description covers the action, scope, permissions, side effects, and all parameter semantics, which is largely complete for invoking the tool. It does not mention return behavior, async behavior, or failure modes, and it does not cite sibling alternatives, so a small gap remains for fully autonomous decision-making.

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 0% description coverage, so the tool description must compensate. It does: every parameter is explained, including defaults for store and semantic_model, the meaning of field, and the explicit allowed model names. This is strong, complete parameter guidance.

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 a specific action and resource: "Enable semantic search for one explicit keyspace." It further differentiates itself with "This tool never enables semantic search database-wide," making the scope unmistakable. The title and body align clearly.

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 clearly implies when to use it: when enrolling a single keyspace for semantic search. It also gives an explicit exclusion: it never enables database-wide semantic search. However, it does not name sibling alternatives explicitly, such as montycat_enable_external_vectors or montycat_disable_semantic, so it lacks full alternative routing.

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