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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the description does not contradict it. The description adds useful context by disclosing the returned fields and the underlying API endpoint, but says nothing about pagination behavior, ordering, or empty-result handling beyond what the schema's limit/offset notes imply.

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 sentences, zero filler: the first front-loads what the tool returns and the second pins the exact endpoint. Nothing is padded or redundant.

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?

With no output schema, the description's enumeration of returned fields (type, date, text, team member) meaningfully compensates, and all three parameters are fully documented in the schema. The remaining gap is usage context — nothing tells the agent when this listing is the right call versus a sibling lister.

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%, with limit, offset, and constituent_id all documented including defaults, ranges, and the 0-based/next_item convention. The description adds no parameter-level meaning beyond that, so the baseline of 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?

The description states a specific verb+resource ('Contact reports logged for a constituent') and enumerates the data returned (type, date, text, team member), which clearly separates it from the sibling listers for notes, gifts, and memberships. It stops short of explicitly naming those siblings, so this is a clear but not maximally differentiated purpose statement.

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?

There is no when-to-use guidance, no prerequisites (e.g., you must have a constituent_id in hand), and no mention of alternatives such as lgl_list_constituent_notes or how to create a report via lgl_create_contact_report. The only routing signal is the resource name itself, which is implied rather than stated.

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