select_page

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

With no annotations provided, the description carries full burden for behavioral transparency. It merely restates the name without disclosing any behavioral traits such as side effects, state changes, or requirements.

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?

While the description is short, it is underspecified and fails to convey essential information. It is not true conciseness because it sacrifices clarity for brevity.

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 presence of 2 parameters, no output schema, no annotations, and many sibling tools, the description is severely incomplete. It does not explain return values, side effects, or the semantics of parameters like pageIndex and selectionMode.

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 description adds no meaning beyond the input schema. The schema's parameter descriptions are minimal ('Page index'), and the 'selectionMode' parameter lacks description entirely. The tool description does not compensate for the 50% 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 'Select a page' is a tautology that merely restates the tool name. It provides no specifics about what 'select' means in this context and fails to distinguish from sibling tools like 'select_page_item', 'select_spread', and 'navigate_to_page'.

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 given on when to use this tool versus alternatives. For example, the difference between 'select_page' and 'navigate_to_page' is unclear, and there are no prerequisites or context provided.

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