asc_list_all_apps_snapshot

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

No annotations provided, so description carries full burden. Discloses that reports are vendor-scoped and merged, and that default date is yesterday in Apple's timezone. Provides adequate behavioral context.

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?

Three sentences, no fluff. Each sentence provides distinct value: definition, functionality, and usage tip. Well-structured 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?

Despite no output schema and no annotations, description explains what data is fetched and what fields are returned. Sufficient for an agent to understand tool's purpose and output. Could be more explicit about response structure.

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?

Only one parameter (reportDate) with schema description covering its format and default. Description adds 'skip reportDate to use yesterday' which aligns with schema. At 100% schema coverage, baseline 3 applies; no additional semantics beyond schema.

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?

Clearly describes a cross-app snapshot that fetches sales and subscription events and merges with app list. Distinguishes from siblings like asc_list_apps, asc_get_sales_report, asc_get_subscription_events by combining multiple data sources.

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?

States to skip reportDate for default yesterday's data, implying use case. Does not explicitly mention when not to use or alternative tools, but context makes it clear for combined data.

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