list_app_infos

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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful scope information by noting that results include the editable next-version record, but it omits pagination behavior, the role of next/limit, and what records are returned beyond that one special case.

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 front-loaded sentence with no filler. Every clause contributes either scope ('app-level information records') or a meaningful detail ('editable next-version record').

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 list tool with pagination parameters, no output schema, and zero schema parameter descriptions, the definition is too thin. It identifies the resource but does not explain return shape, pagination, or how this differs from the many sibling list and get tools.

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 0%, so the description must compensate for undocumented parameters. It says nothing about appId, next, or limit, leaving all three parameters to be understood only from their names and types in 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 uses a specific verb ('List') and resource ('app-level information records') and clarifies that the results include the editable next-version record. It does not explicitly distinguish this tool from close siblings such as list_app_info_localizations or get_app, so it falls short of a 5.

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 gives no when-to-use guidance, prerequisites, or alternatives. With many sibling list/get tools available, an agent is left to infer that this is the app-info listing endpoint rather than, for example, app-info localizations or app versions.

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