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

Annotations supply only destructiveHint=true, which the description does not explain or confirm (e.g., what side effects a logged activity has on linked records, whether participants are notified, or whether calendar/notification fan-out occurs). It does correctly convey that this is a write/POST operation, but adds no auth requirements, side effects, or reversibility detail.

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 compact sentences, front-loaded with the verb and resource; the endpoint mapping is a short trailing clause. Nothing extraneous, nothing buried.

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 with no output schema, the description says nothing about the required 'subject' field, what the call returns (e.g., a new activity id), or error/validation behavior. The high schema coverage and the destructiveHint annotation carry most of the load, leaving this adequate but thin.

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% across all 14 parameters, so the schema already documents each field including enum-like values (time_status, priority 1-5). The description only vaguely gestures at targeting ('against a member, opportunity or project') and participants, adding nothing the schema lacks; baseline 3 applies.

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 ('Log an activity') plus the resource, with the activity kinds (call, meeting, task, note) and the records it attaches to (member, opportunity, project) spelled out. An agent can immediately separate this from the read-only sibling current_rms_list_activities.

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 never states when to use this versus alternatives, and no update_activity sibling exists, so the agent gets no routing rule. Only implied usage is conveyed by the word 'Log', with no prerequisites, sequencing, or when-not-to-use guidance.

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