Huawei App Gallery

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

No annotations provided, so description carries full burden. Provides the 180-day range limitation. Missing details on URL expiration, whether reports are generated synchronously/asynchronously, rate limits, or specific permission requirements.

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 zero waste. Front-loaded with action verb and specific resource. Second sentence provides critical constraint. Every word earns its place.

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?

Appropriate for a report generation tool with 6 parameters but no annotations or output schema. Mentions return value type (URL) but omits behavioral details like URL timeout, report availability delay, or pagination.

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 has 100% coverage, establishing baseline 3. Description adds crucial domain context: the 180-day constraint contextualizes the date range parameters, and 'CSV or Excel' reinforces the export_type enum meanings beyond raw schema values.

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?

Clear verb ('Get download URL') and resource ('app download/install report'). Mentions format options (CSV/Excel). Does not explicitly distinguish scope from sibling 'get_install_failure_report_url' (successful downloads vs failures).

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 critical constraint 'Max 180-day range' for date parameters. Lacks explicit guidance on when to use versus the similar sibling tool (get_install_failure_report_url) and omits mention of the environment variable fallback for app_id.

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