edit_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 behavioral disclosure, but it only states that the tool edits a note. It does not explain whether note_data replaces the entire note, whether partial updates are supported, what permissions are required, what side effects occur, or what the response contains.

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 extremely short and front-loaded, but this is under-specification rather than effective conciseness. Every word merely repeats information already present in the tool name, so it does not earn its place by adding useful guidance.

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?

Given a nested required parameter (note_data) and no annotations, the description is far too thin to support correct invocation. It fails to explain required parameters, update semantics, return behavior, or any operational context needed to distinguish this from other note-related tools.

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 description coverage is 0%, and the description provides no information about group_id, note_id, or note_data. The note_data object has additionalProperties true and is completely undescribed, so an agent has no idea what shape the data must take or how the parameters relate to the edit operation.

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 'Edit a note' is essentially a restatement of the tool name itself, providing no additional detail about what editing entails or which fields can be changed. It does not distinguish this tool from sibling operations beyond the generic verb 'edit', and lacks any specificity about the resource's editable aspects.

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?

No guidance is given about when to use this tool versus alternatives such as create_note, get_note_details, or delete_note. The intended use is only implied by the verb 'edit', with no explicit context, prerequisites, or exclusions.

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