obsidian_search_jsonlogic

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

Annotations already indicate readOnlyHint=true and destructiveHint=false, so the description adds minimal value. It confirms the read-only nature but does not disclose any behavioral traits like response format, performance characteristics, or handling of timeouts.

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 sentence that is front-loaded with the action and resource. No extraneous words or filler.

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 complexity of a JSONLogic query (nested object parameter) and no output schema, the description is insufficient. It does not hint at the structure of the query or what the response looks like, leaving the agent with an incomplete understanding of the tool's usage.

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 0%, meaning the JSON schema does not describe the 'query' object properties. The description does not compensate by explaining what the query parameter should contain (e.g., JSONLogic format) or the purpose of timeoutMs. This leaves the agent with no guidance on parameter semantics.

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 clearly specifies the action (run a JSONLogic query) and the resource (Obsidian Local REST API search endpoint). It distinguishes itself from siblings like obsidian_search and obsidian_search_dataview by explicitly mentioning JSONLogic.

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 like obsidian_search or obsidian_smart_search. No context is given for when JSONLogic is appropriate or what prerequisites exist.

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