obsidian_open_search_in_app

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

With no annotations, the description carries full burden but only states 'Returns success message or error'. It does not disclose whether the app must be running, if it focuses the app, or any side effects like modifying state.

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 at 5 lines, with each sentence contributing essential information (purpose, args, returns). No 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?

While it covers basic inputs and outputs, it lacks context about prerequisites (e.g., app must be running) and potential failure cases. For a simple tool with 2 params, it is mostly complete but could mention the need for Obsidian to be open.

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 description adds meaning to both parameters ('vault: Name or ID of the vault', 'query: Search query to execute') beyond the schema's bare property names, which had 0% description coverage.

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 states the verb 'Open search' and the resource 'in Obsidian with a query'. It distinguishes itself from siblings like obsidian_search_notes which likely return results rather than launching the app's search UI.

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 tool versus alternatives such as obsidian_search_notes or obsidian_focus_app. There are no exclusions or prerequisites mentioned.

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