apex_list_items

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, fully covering the safety profile. The description adds no additional behavioral context, such as filtering behavior, return format, or prerequisites, so it contributes nothing beyond the structured annotations.

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 sentence with no redundant words, immediately and clearly stating the tool's action and target. It is efficiently front-loaded and serves its purpose without unnecessary elaboration.

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 complete input schema, output schema, and safety annotations, the minimal description is largely sufficient for a simple read-only listing tool. It could optionally mention the region_name filter or define 'items,' but the structure already provides the necessary context.

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?

All three parameters are documented with descriptions in the input schema (100% coverage), so the description does not need to add parameter semantics. The description itself mentions no parameters, which is acceptable under the baseline rule for high schema coverage.

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 'items on a page of an existing app,' which distinctly identifies the tool's function. It differentiates well from sibling tools like apex_list_pages and apex_list_regions, making the purpose unambiguous.

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 implies usage through its phrasing ('existing app') but provides no explicit guidance on when to choose this tool over alternatives. There are no exclusions or references to sibling tools, leaving the agent to infer context from the name alone.

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