get_crm_stats

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

No annotations are present, so the description carries the full burden. It only says 'Get aggregate statistics' without explicitly stating that it's a read-only operation, nor disclosing any additional behavioral details such as data freshness, permissions, or limitations. The 'Get' verb implies read-only, but this is not made transparent.

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 directly states the action and resource. It contains no fluff or unnecessary words, making it exceptionally concise.

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?

The output schema exists and presumably defines the return structure, so the description need not explain return values. However, the description does not specify what categories of CRM statistics are included or when it should be used over sibling tools. For a simple read-only tool, it is minimally adequate but would benefit from a bit more detail.

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, and the input schema fully covers the (empty) input. The description adds no parameter-level details, but none are needed. The baseline of 4 for zero-parameter tools applies.

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 action ('Get') and the resource ('aggregate Feather CRM statistics'), providing a specific verb and scope. However, it does not explicitly differentiate from sibling tools like get_connector_stats or get_growth_metrics, relying on the CRM qualifier to do so.

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?

There is no guidance on when to use this tool versus the sibling stats tools. The description states only what the tool does, with no context about selecting it for CRM aggregates specifically, or any exclusions.

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