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

With no annotations, the description carries the burden of disclosing behavior. It conveys that this is a read-only summary operation and lists the types of information returned. However, it does not mention authentication requirements, data scope (e.g., global vs. user-specific), freshness, or response structure beyond the vague 'etc.'.

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 a single, front-loaded sentence that immediately names the action and scope, followed by parenthetical examples to clarify without adding unnecessary length.

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 no-input, read-only statistics tool, the description is reasonably complete: it identifies the tool's purpose and the main output categories. The lack of an output schema and annotations means the description could be more explicit about exact returned fields, but the simple nature of the tool lowers that burden.

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?

The tool has zero parameters, so the baseline is 4. The description adds useful context about what data categories the output will cover, which is the only semantic layer needed.

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 uses a specific verb ('Get') and a clear resource ('CRM statistics and overview'), with concrete examples of what is included (contact counts, activity counts, pending items). This clearly distinguishes it from sibling tools that list individual contacts or activities.

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 implies this tool is for aggregate overviews and counts, not detailed lists, but it does not explicitly state when to prefer this over sibling tools like contact_list or activity_list. The context is clear enough for a simple read-only summary tool.

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