get_app_events

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

No annotations are provided, so the description carries the full burden. It discloses the return format ('JSON string with keys: events (list with type, shop, date), count, app_id'), enumerates all valid event type values, and mentions the default limit. This is solid transparency, though it does not discuss error handling, authentication, or pagination details.

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 well-structured with 'Args' and 'Returns' sections, lists the event types compactly, and contains no filler. It is appropriately detailed without being bloated, making it easy to scan and parse.

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 covers all parameters and return shape, which is sufficient for a read-only event listing operation. It does not mention pagination or how this tool relates to other app-level analytics tools, but given that it has no annotations and a simple schema, this is a minor gap.

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?

The input schema has no descriptions, but the description compensates fully by explaining every parameter: app_id, event_types with the complete list of allowed values, date_from and date_to with format, and limit with default. This gives the agent everything needed to construct correct arguments.

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 begins with 'Get app events (installs, uninstalls, charges, etc.) for a specific app,' which uses a specific verb and resource and clearly distinguishes this tool from sibling analytics tools like get_transactions or get_revenue_summary. The scope is unambiguous: events for a single app.

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?

The description clearly implies when to use the tool: to retrieve events for a specific app, with optional filters by event type and date range. It does not explicitly mention alternatives or when-not-to-use, but the context is clear enough for an agent to select it appropriately among siblings.

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