select_page

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

With no annotations, the description must disclose behavior. It only states the action without explaining side effects (e.g., setting the current page), error handling for nonexistent pages, or whether it returns anything. The description is too terse to inform the agent of behavioral consequences.

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 filler, making it highly concise. However, the brevity comes at the cost of missing essential usage and behavioral information.

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?

The tool has one required parameter and an output schema, but the description lacks critical context about prerequisites and effects. It is not complete enough for an agent to understand when and how to invoke it correctly, especially given its role among page-related sibling 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?

The schema defines a single 'name' string parameter with no description. The description's 'by name' clarifies that the parameter is the page name, but it adds no additional semantics such as format, uniqueness, or validation. Given 0% schema coverage, this is minimal compensation.

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 by name' clearly identifies the action (select) and resource (page), with the parameter 'name' indicating the selection criterion. This distinguishes it from sibling tools like list_pages and add_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 provided on when to use select_page versus alternatives. It does not mention prerequisites such as an open document, whether it changes the active page, or how it relates to list_pages/open_document. This leaves the agent without context for appropriate invocation.

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