gui_selected_notes

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

No annotations are provided, so the description carries the burden. It correctly indicates a read operation returning IDs, but does not disclose error cases (e.g., browser closed, no selection) or whether the response is a list or possibly null. For a simple getter, this is adequate but not thorough.

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?

A single, well-formed sentence that is front-loaded with the action. 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?

The tool is simple with zero parameters and an output schema (not shown), but the description lacks details about return value format, error handling, or what constitutes 'selected.' For a getter, it is minimally viable but could be expanded.

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 tool has no parameters, so schema coverage is 100% trivially. The description adds no parameter details, but none are needed. Baseline at 4 is appropriate.

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 tool returns note IDs from the open Card Browser. The verb 'Return' is specific, and the resource 'note IDs currently selected' is unambiguous. It distinguishes itself from sibling tools like gui_browse (which opens the browser) and gui_current_card (which gets the current card).

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 implies the tool requires an open Card Browser with selected notes, but it does not explicitly state when to use it or what happens if the browser is not open or no notes are selected. No alternatives are mentioned, though the sibling tool set includes find_notes and gui_browse.

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