create_stat_report

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

Description states 'create' which is a mutation, but annotation has readOnlyHint=true. This is a direct contradiction. Otherwise, description adds async/wait behavior details beyond annotations.

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 sentences with a supplementary note. All information is essential and front-loaded.

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?

Covers creation, waiting, download path, and status handling. Complexity is addressed, and output schema is mentioned via downloadUrl. Complete for a tool with these features.

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% with descriptions. Description adds value by specifying date format (YYYY-MM-DD), timezone (KST), meaning of 1 job per day, and listing example report types.

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 tool creates a StatReport job and waits for completion. It distinguishes from sibling download_stat_report by explicitly mentioning the download step.

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?

Provides context on async behavior, 1 job per day, and handling of NONE status. Also directs to use download_stat_report for download. Lacks explicit when-not-to-use but is clear.

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