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

With no annotations, the description carries the full burden. It usefully discloses 'Read-only, free', which is real behavioral context (mutability and cost). But it omits pagination behavior and return-shape expectations for an 8-param history endpoint.

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 core purpose and scope. Minimal waste; the id prerequisite is placed after the main statement, which is sensible.

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 an 8-parameter tool with no annotations and no output schema, the description covers purpose, filtering, and read-only/free status but omits limit/offset semantics and return format. Adequate but with clear gaps against the complexity.

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 38%, so the description must compensate. It maps to channel, replied, and date (from/to) filtering, and implies type via 'campaign or SDR search', but leaves limit and offset entirely undocumented and adds no syntax/format detail.

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+resource ('Every outbound touch for one campaign or SDR search') plus its filter dimensions, which is clear and actionable. It distinguishes itself from crm_communication_cards by naming it as the id source, though it does not explicitly differentiate from crm_communication_thread or crm_get_conversation.

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 a concrete prerequisite workflow ('Use crm_communication_cards first to get the id'), which is genuinely useful guidance. However, it offers no when-to-use vs-when-not guidance against the related thread/conversation siblings, leaving the choice to inference.

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