hourly_reports_get

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

No annotations are present, so the description bears full burden. It merely states 'Get hourly reports', omitting details on read-only nature, pagination (page, page_size in schema but not explained), rate limits, or whether data is aggregated or detailed. The agent cannot judge safety or side effects.

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 very short (two equivalent phrases) but lacks structure. It is concise but at the cost of valuable information. It does not use headings, lists, or examples that could aid comprehension.

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?

Given the tool's complexity (8 parameters, nested objects, no output schema), the description is severely incomplete. It does not explain return format, pagination behavior, error conditions, or how to interpret results. The agent would require additional knowledge to use this tool correctly.

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 63%, and the description adds no parameter explanations beyond what the schema provides. For example, 'level', 'group_by', 'fields', and 'filtering' are not described in the description text, leaving the agent without context on acceptable values or usage.

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 '获取时报表数据 (Get hourly reports)' clearly indicates the tool retrieves hourly report data. It distinguishes from sibling tools like daily_reports_get by specifying hourly granularity, but lacks detail on the report content (e.g., metrics, dimensions).

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 is provided on when to use this tool versus alternatives like daily_reports_get or async_reports_add/get. The description does not mention prerequisites, limitations (e.g., max date range of 3 days per schema), or differentiation between report types.

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