Log activity

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

With no annotations, the description must carry full burden for behavioral traits. It only mentions the write permission prerequisite but fails to disclose success/failure behavior, side effects, or return format. For a mutation tool, this is insufficient.

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?

The description is extremely concise with one sentence plus a prerequisite. However, it is not under-specified; it efficiently states the purpose and a critical requirement.

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?

Despite high schema coverage, the description lacks context on return values, error handling, or usage scenarios. Given 8 parameters and no output schema, the description is too brief to fully inform an agent.

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 coverage is 88%, so most parameters have descriptions in the schema. The tool description does not add any parameter-level information beyond the schema, meeting the baseline of 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?

The description clearly states the verb 'Record' and the resource 'Activity' against a target contact, which is specific and distinguishes from siblings like add_note or create_contact by referencing the CiviCRM Activity entity.

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 notes a prerequisite ('Requires CIVICRM_ALLOW_WRITES=true') but provides no guidance on when to use this tool versus other write tools like civicrm_add_note or civicrm_create_contact, nor does it mention scenarios where logging an activity is appropriate.

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