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

The annotations already cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=false), and the description adds meaningful context beyond them: a non-obvious hidden state transition on another entity (the lead becomes "contacted" on first outgoing contact) and a members-only authorization scope. It stops short of describing repeat-logging behavior or error conditions, so a 4 rather than 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?

Three tight sentences, front-loaded with the action, then the side effect, then the constraint, with a docs link at the end. No sentence is filler and nothing important is 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 6-parameter mutation tool with full schema coverage, annotations, and no output schema, the definition covers purpose, constraints, and the key side effect, which is enough to call it correctly. It leaves minor gaps around whether the tool returns anything and how duplicate entries behave.

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% and every parameter is documented in the schema, including the direction enum meaning and the 30-day-back limit on 'at', so the baseline applies. The description adds only marginal meaning beyond that, mainly tying direction='out' to the "contacted" transition; it says nothing about 'body' length or 'projectId' scope.

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 and resource ("Record a conversation ... in the lead's log") and enumerates the concrete variants (call, WhatsApp, email, meeting, note), which lets an agent distinguish it from the read-side siblings listRikmaLeadsTool and getLeadTool without opening any schema.

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?

Gives real usage constraints: "Only log what the member told you happened; never invent a conversation" and "Members only", plus the side effect that a first outgoing contact marks the lead "contacted". It does not explicitly say when not to use it or name an alternative tool (e.g., reading a lead's log via getLeadTool), which keeps it short of a 5.

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