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

The annotations only declare destructiveHint=true, and the description adds genuine value beyond that by disclosing the super_admin token requirement. However, it says nothing about side effects (record visibility, whether an existing interaction is overwritten) or the response shape for what is a write operation.

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 tight sentences, front-loaded with the action and resource, with optional fields and the auth prerequisite following. The trailing 'TeamUp: POST /crm/interactions' is marginally useful endpoint metadata but borders on filler.

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 four-parameter write tool with no output schema and only a destructiveHint annotation, the description covers the action, the optional fields, the interaction vocabulary, and the token requirement. It is nearly sufficient; only side-effect and response behavior 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 all four parameters (customer, interaction_type, note, call_outcome) are already fully documented in the schema, including the enum values and the 'only for interaction_type=Call' constraint. The description merely summarizes note and call outcome, adding no syntax or format detail beyond the schema.

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 ('Record') and resource ('call, email, meeting or contact with a customer or lead'), with the optional fields named. It is clearly distinguishable from the sibling goteamup_list_crm_interactions by verb contrast, though it never names that sibling 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?

The description states a prerequisite ('Requires a super_admin-level token'), which is useful context, but it gives no explicit when-to-use/when-not guidance or comparison to alternatives such as the list or create_customer tools. Usage is only implied by the verb.

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