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

Annotations already declare readOnly=false, destructive=false, idempotent=false and openWorld=false. The description adds genuinely new behavioral context: the note is visible to the person via get_about_me, is used only to rank and write their own applications, is reversible at any time via confirm_note/delete_note, and returns a summary in `say`. It stops short of stating limits or failure behavior.

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?

Front-loaded with the action and its precondition, then lifecycle and output details. Four dense sentences with little waste, though the final sentence about `say` is terse enough to be slightly cryptic.

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 single-parameter write tool with no output schema, the description covers visibility, purpose limitation, reversibility and the returned `say` summary. No meaningful gaps remain for correct invocation, though input constraints are unspecified.

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, but the name is largely self-explanatory. The description does not define its format or length, only supplying an example of note content ('remember I want to move into management'), which adds moderate value over the bare schema.

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 ('Save a note ... about their job search') and immediately scopes it ('Only when the person says so'). It also names the read counterpart get_about_me, so an agent can distinguish it from the sibling tools that view, confirm, or delete 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?

Gives an explicit trigger condition ('Only when the person says so') plus a concrete example utterance, which also implies when not to call it (unsolicited notes). It names confirm_note, delete_note and get_about_me, covering the surrounding lifecycle so the agent knows where this fits.

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