Disable Semantic Search

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

Beyond the annotations (destructiveHint=true), the description explains the nuanced destructive behavior: vectors are retained unless drop_vectors is set, and dropping is recommended only in specific scenarios like changing embedding models. It also mentions governance enforcement, adding meaningful behavioral context not available from annotations.

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 concise and well-structured: a one-line purpose, two sentences of important behavioral context, and a tight parameter list. Every sentence earns its place, with no filler or repetition.

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's destructive nature, three parameters, and absence of an output schema, the description covers what the tool does, its default non-destructive behavior, when to opt into destruction, and each parameter's meaning. Nothing essential for invoking it correctly is missing.

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 description coverage is 0%, but the description fully compensates with an Args section covering all three parameters: keyspace ('Explicit keyspace to unenroll'), store ('Defaults to the configured store'), and drop_vectors ('Also delete stored vectors for this keyspace'). This adds meaning well beyond the bare schema titles.

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 verb ('Disable'), a clear resource ('semantic search'), and a scope ('one explicit keyspace'). This distinguishes it from siblings like montycat_enable_semantic and montycat_reembed_semantic without needing to open their schemas.

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 gives clear context: stored vectors are retained by default so re-enabling can resume without a full rebuild, and explicitly says to set drop_vectors only when intentionally clearing vectors. It does not explicitly name alternative tools, but the situational guidance is strong enough to guide correct use.

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