Get Daily Stats

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

Annotations already declare readOnly, idempotent, and non-destructive, so safety is covered. The description adds value beyond them by stating there are no arguments and enumerating the returned fields and their breakdown structure, which the annotations do not convey.

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 short sentences, zero waste. What the tool returns and its scope are front-loaded, and the no-argument note follows immediately.

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?

With no output schema, the description compensates by naming the return fields (count, volume_brl, platform_fee_brl) and the payin/payout/daily-total breakdown. Minor gap: 'today' is undefined with respect to timezone, which matters for a day-boundary metric.

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 takes zero parameters, so the baseline is 4. The description correctly and explicitly confirms 'No arguments,' removing any ambiguity for an agent that might otherwise hunt for a tenant or date parameter.

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 and resource ('Get today's volume and platform fees') with clear scope: tenant-level, across payins and payouts, for today. 'Today's' implicitly separates it from ashar_get_monthly_stats, but the description never names that sibling, so differentiation is left to inference.

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?

Usage is only implied by the word 'today's' – an agent can guess this is the daily snapshot versus the monthly one, but the description never says when to prefer this over ashar_get_monthly_stats or whether it is the right tool for a specific date range. No exclusions are stated.

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