apps__app_events__list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the endpoint and clarifies the resource scope ('belonging to an app'), but does not disclose additional behaviors such as pagination, filtering, or response structure beyond what the schema provides.

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 a single concise sentence that front-loads the verb and resource, followed by the endpoint. There is no redundant or extraneous 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 list tool with comprehensive annotations and a well-documented schema (100% parameter coverage), the description adequately conveys purpose and resource. However, it omits any mention of pagination or filtering options directly, though these are present in the schema, making it slightly less complete than ideal.

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?

Although the schema covers all parameters, the description's endpoint ('/v1/apps/{id}/appEvents') disambiguates the 'id' parameter as the app ID, which the schema's description ('ID from the matching list call') fails to convey clearly. This adds meaningful semantic 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?

The description clearly states the action ('List') and the resource ('app events belonging to an app'), with a specific HTTP endpoint. This unambiguously differentiates it from sibling list tools like apps__list or builds__list, which operate on different resources.

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 does not provide any guidance on when this tool is preferable to alternatives, nor does it mention any exclusions or prerequisites. It simply states the core function without contextual direction.

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