asc_get_subscription_events

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

Discloses the default date behavior (yesterday in Apple's timezone) and output contents, but lacks information on read-only nature, authorization requirements, or rate limits. No annotations are provided to supplement.

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 concise sentences with no filler: purpose, output contents, and default behavior. Every sentence adds necessary information.

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?

For a simple single-parameter tool without an output schema, the description adequately explains the return format (per SKU and country) and default behavior, making it effectively complete for use.

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 provides full description of the single parameter, but the tool description adds explicit timezone name (America/Los_Angeles) and clarifies default behavior, offering marginal added value beyond the 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 states it fetches the SUBSCRIPTION_EVENT report for one day, specifying what data it shows (trial starts, conversions, cancels, etc.) and distinguishing from sibling asc_get_subscription_events_range by limiting scope to a single day.

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?

Describes the tool as a convenience wrapper for a single day, implying use for daily reports, but does not explicitly state when not to use it or mention the alternative range tool. The sibling name provides implicit guidance.

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