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

Annotations already declare destructiveHint=true, so the write/mutation profile is covered. The description adds the underlying endpoint (POST /activities) and confirms the activity is associated with a member/opportunity/project, but says nothing about permissions, side effects, or whether the association must pre-exist.

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?

A single front-loaded sentence that names the action and its scope, followed by a brief endpoint note. No filler, though the endpoint reference is marginal value for an agent that cannot read it from the schema.

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 14-parameter mutation tool with no output schema, this description is thin: it never mentions the required 'subject' field, defaults, or what the response returns. It is adequate but leaves real gaps given the tool's complexity.

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 100% with all 14 parameters documented in the schema, so the baseline is 3. The description only hints at the regarding_* target types and optional participant_member_ids, 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?

States a specific verb (log) plus resource (activity) and enumerates variants (call, meeting, task, note) and target records (member, opportunity, project). This clearly separates it from siblings like current_rms_list_activities, though it doesn't name 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?

No when-to-use or when-not-to-use guidance, no prerequisites, and no pointer to alternatives such as current_rms_list_activities for reading. The '(optionally with participants)' clause is the only usage-flavored content.

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