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

Annotations already declare readOnlyHint=true, so the read safety profile is covered. The description adds genuinely useful context beyond that: the required super_admin-level token (an auth gating detail not in the annotations or schema) and the underlying endpoint. It stops short of describing pagination or return format.

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?

One tight sentence, front-loaded with the core purpose, then the auth prerequisite and endpoint. No redundant or filler content, though the trailing API reference is marginal value.

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 read-only list tool with a fully documented schema and no output schema, the description covers purpose, the optional customer scope, and the super_admin auth requirement. Nothing essential for correct invocation is missing.

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 five parameters (page, expand, fields, customer, page_size) are documented in the schema itself. The description only adds a plain-language gloss for the customer filter, which is the correct 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+resource ('List logged CRM interactions') and even enumerates the interaction types (calls, emails, meetings, contacted) plus what fields come back (notes, logger). It implicitly contrasts with the sibling goteamup_log_crm_interaction via the List/Log verb, but never names or explicitly differentiates that alternative.

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?

It states a real prerequisite ('Requires a super_admin-level token') and hints at an optional filter usage ('optionally for one customer'), which is useful context. However it gives no explicit when-to-use/when-not guidance and does not point to the sibling log tool as the write counterpart.

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