kms_multimodal_search

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

No annotations are provided, so the description carries the full burden. It discloses that it retrieves 'full content' and detects technical content across modalities, which is useful behavioral context. However, it says nothing about rate limits, permissions, result ordering, or whether results are deduplicated across content types.

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?

Two sentences, tightly front-loaded with the core purpose first and modality/technical-detection details second. Minimal waste, though the second sentence is somewhat dense with comma-separated features.

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?

For a 4-parameter search tool with nested filters, 100% schema coverage, and no output schema, the description is adequate but lacks crucial routing information: when to use this vs kms_search / kms_intelligent_search. An agent has enough to invoke it but not enough to confidently select it.

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 100%, so the schema already documents all four parameters and their semantics. The description adds no parameter-level detail beyond what the schema provides. Baseline 3 is appropriate when the schema does the heavy lifting.

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?

States a specific verb and resource: 'Enhanced multi-modal search with full content retrieval', and specifies the modalities covered (text, audio, video, video frames) plus technical content detection. Clear purpose, though it doesn't differentiate itself from siblings like kms_search or kms_intelligent_search.

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 when-to-use or when-not-to-use guidance is provided. The description doesn't explain how this differs from kms_search or kms_intelligent_search, leaving the agent to infer or guess which sibling to choose.

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