apex_list_pages

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

The tool is annotated as read-only, idempotent, and non-destructive, which the description aligns with ('List'). The description adds minimal behavioral context beyond the annotations, such as the ability to target the current session or a specified app_id, but no additional operational details like pagination or filtering.

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, clear sentence that front-loads the core function. No wasted words.

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 listing tool with a single optional parameter and an output schema, this description is sufficient. It conveys the core purpose and scope, and the output schema can define the return structure.

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 only parameter, app_id, is fully described in the schema with its default behavior. The description doesn't add further semantic detail beyond what the schema provides, so it meets the baseline 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 clearly identifies the action ('List'), the resource ('pages'), and the scope ('current session or an existing app'). It distinguishes from sibling tools like apex_describe_page, which describes a specific page, though it could be more explicit about what page information is returned.

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 use cases: when you need to list pages for the current session or a given app. However, it doesn't explicitly state when not to use it or mention alternatives such as apex_describe_page for page details.

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