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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds genuine value beyond them by disclosing the returned shape (author, category, content) and the underlying endpoint, which matters because no output schema exists. It doesn't mention pagination behavior, but the schema's next_page note partly covers that.

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 purpose and return fields, with the endpoint appended as compact supplementary detail. Nothing is redundant or padded.

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 read-only list tool with full schema coverage and annotations covering the safety profile, the description supplies the essential missing piece — what each note contains. No output schema exists, so this return-shape detail is what completes the picture; only pagination nuance is left implicit.

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 100%, so all three parameters (deal_id, page, per_page) are already documented with defaults and ranges in the schema. The description adds no syntax, format, or constraint detail for any parameter, so this sits at the standard baseline when the schema does the heavy lifting.

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 gives a specific verb and resource ('List the notes (activities) logged on one deal') and scopes it to a single deal, which implicitly separates it from the sibling list_notes and list_person_notes. It stops short of naming those siblings explicitly, so an agent must infer the distinction rather than being told.

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 implied by the phrase 'logged on one deal' — the tool is for notes attached to a specific deal — but there is no explicit guidance on when to prefer it over pipelinecrm_list_notes or pipelinecrm_list_person_notes. No exclusions or prerequisites are stated, so the agent must derive routing from the scope wording alone.

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