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 'large' qualifier, which warns about output size—useful behavioral context. However, it does not disclose pagination, response limits, or performance implications beyond 'large.' With annotations providing the core safety traits, this partial additional context merits a 3.

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 extremely concise—a 4-word phrase—with no filler or redundant information. Every word adds value: 'Full' indicates completeness, 'app list' identifies the resource, and 'large' provides a key output warning. It is tightly front-loaded and wastes zero space.

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 tool has zero parameters, a rich output schema, and strong annotations (read-only, idempotent, non-destructive), the description is largely complete for a list retrieval tool. The 'large' warning is the main missing piece that could be elaborated (e.g., whether pagination is needed), but the presence of an output schema and annotations reduces the burden. It is adequate but could add one sentence about output size/limits.

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 zero parameters, so per the baseline for 0-parameter tools, the description does not need to explain parameters. The description adds no parameter information, but none is needed. The baseline of 4 applies because no parameter semantics are required.

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 'Full app list (large)' clearly identifies the resource (app list) and scope (full/large), distinguishing it from sibling tools like app_details and app_news. However, it lacks an explicit verb (e.g., 'returns' or 'lists'), so it is not a complete verb+resource statement.

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?

No guidance is provided about when to use this tool instead of alternatives. It does not mention that app_details is for a specific app or that app_news provides news, nor does it suggest situations where the full list is appropriate. The description simply states what it is, with no comparative or contextual guidance.

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