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

Annotations only supply destructiveHint=true, so the description's addition of the required super_admin token level and the underlying POST /crm/interactions endpoint adds real behavioral context (mutation + privilege requirement). It does not address side effects on the customer record or whether the logged interaction can be amended/removed, keeping it short of a 5.

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 operation and its scope come first, the auth requirement and API endpoint follow. Every clause carries information an agent can act on.

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 write tool with no output schema, the description covers operation, required privilege, and parameter conditionality, which is adequate. It stops short of describing what the mutation affects or returns implicitly (e.g., new interaction id), leaving a small gap against destructiveHint=true.

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 four parameters (including enum semantics) are already documented in the schema. The description's mentions of an optional note and call outcome restate the schema rather than adding syntax, format, or constraint detail, matching the baseline 3.

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?

Specific verb+resource: 'Record a call, email, meeting or contact' makes the write-side counterpart to goteamup_list_crm_interactions obvious, and the enumerated types mirror the interaction_type enum. It is clear what the tool does, though it never explicitly names the read sibling as the 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?

The description gives one real usage constraint ('Requires a super_admin-level token') and a conditional rule ('call outcome — only for interaction_type=Call'), which is genuinely useful. However, there is no when-to-use vs alternatives guidance and no stated preconditions beyond auth, so it is implied rather than explicit.

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