upnote_open_note

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It only says 'Open a note in the UpNote app by id' and does not mention side effects, whether it launches a UI, what happens for invalid IDs, or whether it requires a locally installed app. The agent is left to guess.

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, direct sentence with no filler. It conveys the essential action and input efficiently.

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 very simple one-parameter tool, the description provides the minimal viable information: what happens and which input is needed. However, it lacks guidance on distinguishing it from upnote_get_note and any behavioral expectations, so it is not fully complete.

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 schema only defines 'id' as a required string, and the description offers no additional meaning beyond 'by id'. It does not explain where the ID comes from, its format, or how to obtain it, so the 0% schema coverage is not compensated.

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 action ('Open a note'), the resource ('a note'), and the required input ('by id'), so an agent knows what the tool does. It does not explicitly contrast with the sibling upnote_get_note, though 'in the UpNote app' hints at opening the UI rather than just fetching data.

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?

There is no guidance on when to use this tool instead of alternatives like upnote_get_note or upnote_search_notes. The description simply states the action without any context about preferred use cases or exclusions.

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