Manage remio note collections

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, signaling a non-read-only but non-destructive mutation. The description adds a valuable behavioral detail: adding by collection title auto-creates the collection if it doesn't exist. This goes beyond the annotations and describes a side effect not otherwise known.

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 two sentences, with the most important action stated first. Every word contributes meaning, and there is no redundant filler. It is concise and well-structured.

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?

With 5 parameters, no output schema, and 0% schema description coverage, the description is too minimal to be complete. It doesn't explain the purpose of 'confirm', how to specify which collection when both ID and title are available, or what happens on removal when no collection is specified. The tool's full behavior is not adequately captured.

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 coverage is 0%, so the description must compensate for documenting parameters. It explains that 'collection_title' can be used for adding and creates the collection if missing, but it does not explain the 'confirm' boolean, the relationship between 'collection_id' and 'collection_title', or the semantics of 'note_id' and 'action' beyond what the schema already shows. Many parameters remain underspecified.

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's function: 'Adds or removes a note from a collection.' This uses a specific verb and resource, and the additional detail about creating a collection by title adds precision. It is easily distinguished from sibling tools like searching or reading notes.

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 usage: you use this tool when you need to add or remove a note from a collection. However, it does not explicitly state when to prefer this over sibling tools, nor does it mention any prerequisites or exclusions. No alternatives are named, so guidance is only implied.

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