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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, yet the description still adds real value: newest-first ordering, the fact that notes are preserved and never overwritten, the workspace-reachability constraint, and what mode='summary' returns. That is genuine behavior beyond the annotation triple.

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?

The purpose is front-loaded in the first clause and every subsequent sentence adds a distinct fact (read-only, preservation, scoping, paging, projection, summary mode). It is dense and slightly run-on but there is little dead weight.

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 read with no output schema, the description does a good job describing the returned content and ordering. The gap is that the paging/projection/summary options it advertises are not backed by the schema, leaving ambiguity about what the tool actually accepts.

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 0%, so the description carries the burden — and it partially does, but it describes 'limit', 'cursor' (next_cursor), 'fields' and mode='summary' that do not exist in the input schema, which declares only lead_id with additionalProperties=false. It also gives no format guidance for lead_id (integer vs string). An agent following the description would pass parameters the schema rejects.

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?

Concrete verb+resource: 'the activity feed of a CRM lead' composed of the caller's logged notes plus status-change history, newest first. An agent can picture the payload immediately. It does not, however, distinguish itself from the sibling get_lead_timeline, which an agent could plausibly confuse with an activity feed.

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 context is implied well ('read-only', 'only the caller's own workspace is reachable', requires 'lead_id'), but there is no explicit when-to-use / when-not-to-use statement and no named alternative despite get_lead and get_lead_timeline sitting in the sibling set. The agent is left to infer the boundary.

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