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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered and the description doesn't contradict it. The description adds the REST endpoint path but nothing about result ordering, whether notes include activity subtypes, or pagination behaviour beyond what the schema states.

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 with the purpose front-loaded and no filler. The trailing endpoint reference is mildly redundant with the structured fields but costs almost nothing.

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?

A read-only, single-scope list tool: annotations carry the safety profile, the schema documents every parameter, and no output schema means return-shape detail isn't required. Only the absence of any routing against list_notes/list_deal_notes keeps it from being fully complete.

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% — person_id, page and per_page all carry clear inline descriptions including the 'Pass the previous reply's next_page' chaining hint. The description adds no parameter detail, so the baseline 3 applies.

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 — 'List the notes (activities) logged on one person' — plus the underlying endpoint GET /people/{id}/notes, which pins down the exact scope. It implicitly separates itself from list_notes and list_deal_notes via 'on one person', but never names those siblings in contrast.

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 by the scoping phrase 'logged on one person'; an agent can infer this is the per-person variant but gets no explicit rule for when to prefer it over pipelinecrm_list_notes or pipelinecrm_list_deal_notes. No prerequisites, no when-not guidance.

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