Close Active File

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

Adds significant detail beyond annotations: explains it is UI-only with no deletion/saving/modification, no-op behavior, return value {ok:true}, error conditions (plugin unreachable), and that it is not affected by vault.select. All these traits are not captured by 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 yet comprehensive, front-loaded with the main purpose, then adding clarifications, use cases, and caveats. Includes an example. Every sentence adds value without 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?

For a simple tool with no parameters and an output schema, the description covers all necessary aspects: behavior, edge cases (no-op, errors), dependencies, and relationships to other tools. It is complete and easy to understand.

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?

With zero parameters and 100% schema coverage, the baseline is 4. The description adds no parameter info (unnecessary) but explains the tool's effect without referencing inputs, which is sufficient.

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 'Close whatever file is currently active in the Obsidian UI,' specifying the verb and resource. It distinguishes from sibling tools like workspace.openFile and workspace.activeFile, and clarifies it is UI-only with no file modifications.

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?

Explicitly states when to use: 'Use after workspace.openFile when you want to dismiss a temporarily-revealed note.' Also suggests pairing with workspace.activeFile first to know what was closed, and notes it is a no-op when no file is active. Provides clear context and excludes misuse.

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