Navigate Obsidian History

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

Annotations indicate readOnlyHint=false and openWorldHint=true. The description adds behavioral details: 'No-op when the stack is empty', 'Requires the Local REST API plugin', and 'Not affected by vault.select'. This provides context beyond annotations, though it could mention error behavior if plugin missing.

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?

Three sentences, each adding essential information. First sentence states purpose, second explains parameters and no-op behavior, third clarifies external dependencies and routing. No wasted words.

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 navigation tool with one parameter, the description covers purpose, behavior, plugin requirement, and relationship to other tools. It has an output schema (not shown), so return values are documented elsewhere. Complete for the tool's complexity.

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 has one parameter with enum and description. The description adds explicit examples: 'direction:'back' = back one step; direction:'forward' = forward one step', which clarifies the effect of each enum value beyond the schema's description.

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 'Navigate the Obsidian back/forward file history, like the arrow buttons in the top-left.' This is a specific verb and resource, and it distinguishes from sibling tools like workspace.openFile or vault.select by mentioning it is not affected by vault.select.

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 explains when to use the tool (to go back/forward in history), provides example parameter values, and mentions prerequisites (Local REST API plugin). However, it does not explicitly list alternatives or when not to use it, but given the unique functionality among siblings, this is sufficient.

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