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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds a meaningful access-control constraint (only the caller's own links are returned, never another user's) and discloses the record types returned plus the title/snippet payload. It does not mention pagination behavior or a default page size, which leaves a minor gap.

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 definition is front-loaded, with the payload description leading and the scoping constraint before any edge detail; nothing is padded. The short sentence 'Pass lead_id' restates a required parameter the schema already enforces, which is the only wasted line.

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 five-parameter read tool with no output schema, the definition covers purpose, privacy scope, and the shape of returned rows, which is enough to call it correctly. Pagination and the limit default remain unstated, but cursor and mode are self-documented in the schema.

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 60%, with mode, cursor, and fields documented in the schema but limit left undocumented. The description names only 'lead_id' and adds no syntax or meaning beyond the schema, so it neither compensates for the gap nor repeats what is already there.

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: lists the caller's personal records (notes/tasks/meeting notes) linked to a CRM lead, and previews the return shape (linked object's title plus snippet). It also bounds scope to the caller's own links only, which separates it from lead-wide tools like get_lead_timeline, though it never names an alternative 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?

Usage is only implied: it says to pass 'lead_id' and that only the caller's links come back, which suggests a personal-links lookup. There is no explicit statement of when to prefer this over get_lead, get_lead_timeline, or list_lead_activity, so the agent must infer the boundary.

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