apps__app_infos__list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds the 'belonging to an app' scope and the GET endpoint, but does not disclose pagination or include/fields behavior beyond the schema. This adds some context but not rich behavioral detail.

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?

One concise sentence plus an endpoint reference. No wasted words, front-loaded with the core action. Ideal for quick AI parsing.

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?

Given the annotations and full schema coverage, the description is sufficient for a list operation. It clearly identifies the resource and scope. The absence of an output schema is mitigated by the verb 'List' implying a collection return. A bit more on pagination or defaults would be helpful, but not essential for this simplicity level.

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 description coverage is 100% for all five parameters. The description does not add any parameter-specific meaning, but the schema already documents attributes like 'limit', 'include', 'next_url', and 'fields_appInfos'. Baseline 3 is appropriate since the schema carries the parameter documentation burden.

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 uses a specific verb ('List') with a clear resource ('app infos') and scope ('belonging to an app'). This distinguishes it from singular get/update operations like app_infos__get and app_infos__update, and the endpoint reference reinforces the action.

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 indicates when to use this tool: when wanting all app infos for a given app. It does not explicitly mention alternatives or exclusions, but the context is unambiguous and the sibling list shows related getters for single app infos, making the usage intent clear.

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