Get today and yesterday statistics

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

No annotations provided, and the description does not disclose behavioral traits such as data source, required permissions, rate limits, or what exactly 'core statistics' includes. Burden falls entirely on description, which fails to inform agents about important behavior beyond basic functionality.

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 unnecessary words. Efficiently conveys the core purpose without extraneous detail.

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?

Lacks details on return value, data scope, and usage examples. Given no output schema and many sibling tools, the description is insufficient to fully understand the tool's output and appropriate use cases.

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?

Single parameter appkey has a useful description explaining default behavior when omitted (UMENG_DEFAULT_APPKEY). This adds value beyond the schema, which only defines type. Schema coverage is 100%, but the description enhances usability.

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?

Description clearly states the action (get) and resource (today and yesterday core statistics for a specific appkey). The time period is specific, distinguishing it from daily data tools. However, 'core statistics' remains vague and siblings like 'umeng_uapp_get_today_yesterday_data' exist without clear differentiation, slightly reducing clarity.

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 such as 'umeng_get_daily_data' or individual day tools. Agents have no context for selecting this over closely related siblings.

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