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

Goes well beyond the annotations: ordering (newest first), actor attribution including agents acting for a person, before/after payloads, the special meaning of field.deleted (values retained, reversible), the audit-log entitlement requirement, and cursor-based pagination. It also flags CRM field values as untrusted content, which is a genuine operational caveat the annotations never convey.

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 tight paragraphs with the core behavior front-loaded and the safety warning separated out. Slightly dense in the first sentence's enumeration, but little wasted text.

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?

No output schema exists, and the description compensates by describing what each entry contains (who, before/after) and the pagination field name. Access prerequisites are covered; the only real gap is the meaning of several filter parameters.

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 only 17% (just workspaceId), so the description carries most of the burden. It clarifies cursor round-tripping via nextCursor and gives semantics for one action value, but limit, actions (a 32-value enum), targetId, and actorMemberId are left unexplained in both schema and description.

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 + resource (lists recorded access/role/permission changes) with explicit scope: newest first, actor attribution, before/after values. It clearly differs from record-oriented siblings such as get_timeline, get_record_lifecycle, or list_deleted_records.

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?

States a hard access precondition — 'Workspace admins on a plan with the audit log only' — which tells the agent when the call will succeed. It does not name an alternative tool or an explicit when-not case against siblings like get_timeline, so it stops 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.