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

Annotations already declare the operation as read-only, idempotent, non-destructive, and closed-world, so safety is covered. The description adds genuinely non-obvious context that annotations cannot: these notes are internal, invisible to the prospect, and have no effect on sending. It does not mention ordering, pagination, or what the returned note objects look like.

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 short sentences, front-loaded with the core resource definition and followed immediately by the visibility constraint and the sibling alternative. Every sentence earns its place and there is no repetition of structured fields.

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 simple one-parameter read-only list tool whose schema and annotations are complete, this description supplies the important domain semantics and the key alternative. The main omission is return-shape or pagination context, but with no output schema and a highly constrained operation, this is a minor gap.

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?

There is only one parameter, and the schema already fully documents it, including that the lead id comes from `lead_list`. The description adds no additional meaning about the `leadId` parameter, so this sits at the baseline for complete schema coverage.

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 clearly establishes that this tool deals with internal notes about a lead, and it distinguishes that resource from prospect-facing messages by naming `conversation_get`. It does not explicitly state that it lists/returns all notes, nor does it distinguish itself from sibling mutation tools like `lead_note_add` or `lead_note_update`.

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?

It gives an explicit alternative for the most likely confusion point: if you want the actual exchanged messages, use `conversation_get`. It stops short of saying when to use `lead_note_add`/`lead_note_update` instead, so the routing guidance is good but not exhaustive.

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