profile_notes_append

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

With no annotations supplied, the description carries the burden, and it does disclose two real traits: the operation appends rather than overwrites, and content is preserved verbatim in notes.md (no parsing or normalization). It does not say what the call returns, whether entries get timestamps/ordering, or whether there are size limits or auth requirements.

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?

Two short sentences, front-loaded with the action and the content, followed by the storage behavior. No filler and nothing that could be cut without losing information.

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 one-parameter append tool this covers purpose, content expectations, and destination, which is the essential minimum with no output schema to explain returns. It is still thin for a mutation tool with zero annotations: the return value and any behavioral side effects (ordering, per-user scoping of notes.md) are unstated.

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% for the single `text` parameter, so the description must compensate. The examples (onboarding answers, voice-note transcripts) usefully constrain what should be passed, but there is no guidance on formatting, maximum length, or whether markdown/whitespace is preserved.

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?

States a specific verb and resource ("Append raw notes from the user") and clarifies what counts as raw notes with concrete examples (onboarding answers, voice-note transcripts). The verbatim/notes.md detail implicitly separates it from structured siblings like profile_add_item, but no sibling is named explicitly, so it stops short of a 5.

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?

Usage is only implied: "raw notes" and the parenthetical examples suggest this is for unstructured user-supplied text rather than structured profile fields. There is no explicit statement of when to prefer profile_add_item/profile_update over this tool, and no exclusion or precondition is given.

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