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

Annotations already cover read-only, idempotent, non-destructive, closed-world behavior, so the description's job is narrower and it delivers extra context: a members-only authorization requirement, an explicit PII handling warning (phone/email never to be copied elsewhere), and log ordering (most recent first). It stops short of covering payload size, truncation, or not-found behavior.

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?

Front-loaded with the verb and resource, then a single dense enumeration of returned fields; the members-only gate and docs link are cleanly separated. The long em-dash parentheticals make it heavier than necessary, but each listed item carries useful selection signal.

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?

With no output schema, the description compensates by enumerating return contents and log ordering, and it flags the authorization and sensitivity constraints for this read tool. Missing only edge-case behavior (lead not found, access denied, log truncation beyond logLimit).

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 three parameters (projectId, leadId, logLimit with default 20 and max 100) are already documented. The description only indirectly touches parameters by noting the log is most-recent-first, which gives ordering context for logLimit but nothing 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?

"Open one lead of a rikma" gives a specific verb and singular resource, and the enumeration (identity/contact, request, stage, owner, next step, follow-up date, linked orders, log) tells an agent exactly what comes back. The singular framing plus the leadId schema hint clearly separates it from listRikmaLeadsTool.

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?

Usage is implied: fetch one lead's full record when you already have its id. There is no explicit when-to-use/when-not guidance and no named alternatives (e.g. listRikmaLeadsTool to find ids, logLeadActivityTool to add entries), only a hard "Members only" gate.

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