get_reports

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

No annotations are provided, and the description does not disclose any behavioral traits such as authentication requirements, rate limits, or whether the operation is read-only. For a list query, it is implied to be safe, but the agent receives no explicit confirmation.

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 extremely brief—one phrase in Chinese. While concise, it may be too minimal for an English-based agent to interpret without translation. The structure is simple, but a slightly more informative description would be more helpful without sacrificing conciseness.

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?

The description lacks context about output format, pagination, or filter usage. With two parameters including a nested object, more explanation is needed for an agent to correctly invoke the tool. The absence of an output schema further increases the need for descriptive completeness.

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%, and the schema descriptions for 'filter' and 'limit' are adequate. The tool description does not add any additional meaning beyond the schema, which is acceptable given the high coverage, but it does not enhance understanding of parameter 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 '查询报表列表' indicates a query/list action for reports, which is clear for a basic purpose. However, it does not differentiate from sibling tools like get_report_by_id or execute_report, which could cause confusion. A more specific description noting that it returns a list would improve 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?

There is no guidance on when to use this tool versus alternatives like get_report_by_id or execute_report. The absence of usage context leaves the agent uncertain about how to select this tool among many report-related functions.

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