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

readOnlyHint=true already covers the safety profile, so the bar is lower, and the description adds real context beyond it: an authorization requirement (super_admin-level token) and the shape of the payload (notes, who logged them). It does not mention pagination behavior or result ordering, but the auth disclosure is the kind of pre-flight constraint an agent needs.

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, front-loaded with the resource and its contents, then the two practical constraints (filter, auth). Slightly redundant to repeat 'TeamUp: GET /crm/interactions' since the name already implies it, but nothing wastes meaning.

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 carries return-value burden and does so by naming the interaction types and the included metadata. Combined with the auth requirement and the fully covered input schema, an agent has enough to call it correctly; only pagination/ordering semantics are left unstated.

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 page, page_size, expand and fields are already fully documented with formats and bounds. The description's only parameter-level addition is glossing the customer filter, which merely restates the schema's own text. Baseline 3 is correct 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?

States a specific verb (List) and resource (logged CRM interactions) and even enumerates the interaction types (calls, emails, meetings, contacted), so the agent knows exactly what comes back. It does not explicitly name the write counterpart (goteamup_log_crm_interaction), but 'logged' plus the list verb clearly separates reads from that sibling.

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?

Adds one useful usage cue — 'optionally for one customer' — signaling the customer filter is the only narrowable dimension. However it gives no explicit when-to-use vs the log_crm_interaction sibling or other list tools, and the super_admin prerequisite is stated only as a requirement, not a decision rule. Implied usage only.

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