search_moments_advanced

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the tool combines search types but does not clarify whether filters are ANDed or ORed, how semantic search interacts with regex, or what output format to expect. There is no mention of read-only status, rate limits, or edge cases. This leaves significant ambiguity for a tool with seven parameters.

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 extremely concise—a single sentence fragment. While it has zero waste, it is under-specified for a tool with seven parameters. It front-loads the key idea but sacrifices necessary detail, making it more cryptically brief than appropriately concise.

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 complexity (7 parameters, no output schema, no annotations), the description is incomplete. It fails to explain how the search modes combine, how results are ordered or limited, or what response structure to expect. The agent is left with insufficient context to invoke this tool reliably, especially compared to sibling tools.

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 baseline is 3. The description adds minimal value beyond the schema—it groups 'query' as semantic, 'regex' as text pattern, and 'tags/kinds/dates' as filters, but this is already evident from parameter descriptions. It does not clarify parameter combinations or provide practical usage examples.

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 'Combine semantic, filters and regex search' clearly indicates this tool performs search functionality combining these three modes. It implicitly references moments from the tool name and distinguishes from the simpler 'search_moments' sibling. However, it lacks an explicit mention of the resource ('moments') and could be more specific about the combination semantics.

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 advanced search versus the sibling 'search_moments' or 'list_moments'. The name suggests advanced usage, but the description does not articulate specific scenarios, prerequisites, or exclusions. The agent receives no help choosing between alternatives.

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