get_smart_followup_stats

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

No annotations are provided, and the description does not disclose behavioral traits. It does not state that the tool is read-only, whether it requires specific permissions, or if pagination is implicit. The term 'stats' implies read-only, but this is not explicit.

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 concise, listing key statistics in a single sentence. However, the trailing '[query]' appears to be a placeholder and may confuse users slightly. It is otherwise well-structured and front-loaded with the tool name.

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 stats tool with 8 parameters and no output schema, the description covers what metrics are returned but lacks details on output format, pagination behavior, or prerequisites. It is adequate but not fully complete.

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 input schema has 100% coverage with descriptions for each parameter. The description adds no extra parameter meaning beyond listing the output metrics. Baseline of 3 is appropriate since the schema already documents the parameters clearly.

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 it provides Smart Follow-up statistics, specifically sales recovery metrics like conversion funnel, response rate, etc. This distinguishes it from siblings like get_smart_followup_config (configuration) and get_smart_followup_logs (logs).

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?

No guidance on when to use this tool versus alternatives. For example, it does not mention that get_smart_followup_config should be used for viewing settings, or that get_smart_followup_logs is for detailed logs. The description only explains what the tool does, not when to choose it.

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