crm_export_audit_log

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

The description goes far beyond the annotations. It discloses that the tool is entirely local and reads an in-memory buffer, makes no HubSpot call, requires no scope, includes even denied/error calls, redacts email/phone, and explains the buffer is not persisted across restarts. These details fully characterize behavior, aligning with and expanding upon the read-only and idempotent hints.

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?

The description is well-structured and efficient. The first sentence states the core function, the second provides use cases, and the remaining sentences deliver behavioral details without redundancy. Every sentence earns its place, making it concise despite being detailed.

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?

Even with no parameters and an output schema present, the description covers all necessary context: purpose, use cases, input (none), output format and content, behavioral traits, redaction, and session-scope limitations. It is fully self-contained and leaves no significant gaps for the agent.

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?

With zero parameters, the baseline is 4. The description doesn't need to explain parameter semantics; it adds value by describing the output format and content, which is appropriate for a no-input tool.

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?

The description clearly states the tool exports the session's audit trail as JSON Lines with one record per line. The verb 'export' and resource 'audit trail' are specific, and the format 'JSON Lines' adds clarity. This is distinct from sibling CRM tools that focus on contacts, deals, and pipelines.

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 provides explicit when-to-use guidance: 'Use this to hand a reviewer evidence... or to attach the trail to a ticket or change record.' It does not mention exclusions or alternative tools, though no alternatives likely exist in the given sibling set, so the absence is not a significant gap.

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