wealthbox.notes.update

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention whether the update is partial or full, whether it overwrites existing content, permission requirements, rate limits, or side effects. The 'raw body' option is mentioned but its behavior is not disclosed.

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 concise, with two sentences. The first states the purpose and the second gives parameter options. There is no irrelevant information, and the key information is front-loaded.

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 no annotations, no output schema, and a nested body object, this sparse description leaves important gaps. It does not explain what a 'raw body' should contain, what the tool returns, or error conditions. The description is too minimal for a tool with such an open-ended parameter like body.

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 description adds some meaning by stating that content can be passed directly or via a raw body, mapping to the schema's content and body properties. However, it does not clarify what 'raw body' entails, and with 0% schema description coverage, the ambiguity around the body object (additionalProperties: true) is not resolved.

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 starts with 'Update note content by id,' clearly stating the action (update) and target (note content) with the unique identifier. This distinguishes the tool from sibling note tools like list, get, and create, and the wording is specific to the update operation.

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 offers usage guidance by explaining that you can pass {content} directly or a raw body, but it does not explicitly state when to use this tool versus alternatives like create or the generic wealthbox.request tool. It implies usage for updating existing notes but lacks exclusionary guidance.

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