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

Annotations confirm it is a write with destructiveHint=true, and the description substantively explains the destruction: 'saving again replaces it' tells the agent prior saved voice is overwritten. It also notes persistence ('kept and reused for every note') and cost ('Free'), adding context beyond the annotation flags.

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?

Three tight sentences, front-loaded with what it does, then the platform caveats, then persistence and cost. The parenthetical platform detail is dense but earns its place; nothing is wasted.

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 6-param mutation tool with no output schema, the description covers purpose, per-platform sourcing, overwrite behavior, and cost. It lacks only an explicit note on what a first save requires or returns, which is minor given no output schema exists.

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 83%, so the schema already documents most parameters (rules, handle, sample, summary, examples). The description clarifies the platform enum's sourcing behavior but adds no syntax or format detail for the required 'sample'/'summary' fields, so the baseline 3 holds.

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: 'Store how the founder writes on one platform'. The purpose (capturing writing voice) is clear and distinct from note-saving siblings like notes_save/notes_context, though it never names a sibling to route the agent explicitly.

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?

Adds real operational guidance on how to source samples per platform (X profile in Chrome, Reddit paste because Claude cannot open Reddit), but gives no explicit when-to-use vs when-to-skip signals or alternatives among siblings.

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