get_statistics

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

With no annotations, the description must cover behavior. It states it 'gets a report' but does not disclose read-only nature, pagination behavior (only schema mentions rrdid as cursor), or what happens on missing data. Behavioral traits beyond the schema are absent.

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?

Single sentence with no wasted words, but overly terse. It could include more structured guidance without becoming verbose. Front-loads the core purpose, but lacks detail that would aid agent selection.

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 4-parameter tool without output schema or annotations, the description is incomplete. It does not specify what fields the report contains, how to interpret results, or any limitations. The agent has insufficient information to decide if this tool meets its need.

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 100%, so baseline is 3. The description adds 'by period' tying to dateFrom/dateTo, but does not enrich meaning beyond schema descriptions already present. No additional formatting, constraints, or usage hints are provided.

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 identifies the tool as retrieving a 'realization (sales) report by period,' specifying the resource ('statistics' as sales report) and the period constraint via date range parameters. However, 'realization' is jargon that could be clarified, and it does not differentiate from sibling tools like get_sales or get_orders.

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. The description does not mention prerequisites, exclusions, or scenarios where get_sales or other report tools would be more appropriate. Context is only implied by the period parameters.

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