pbi_goto_page

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

No annotations provided, so description fully bears responsibility. Details timing: returns on tab switch but canvas may still render, waitReady blocks up to 30s. Discloses error behavior: returns closest candidates on not-found. Fully transparent.

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?

Two sentences with no waste. First sentence defines core function; second sentence packs behavioral details, blocking option, and error handling. Front-loaded and efficient.

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?

No output schema, yet description explains return behavior (closest candidates on not-found). Covers navigation, timing, blocking, error recovery. Siblings include many tools but this one is self-contained. Complete for an action tool.

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?

Schema description coverage is 100%, so baseline is 3. Description adds value by explaining the effect of waitReady (blocking vs non-blocking) and the return timing context, which goes beyond the schema's parameter descriptions.

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?

Clearly states navigate to a page by exact name. Verb and resource are specific. Distinguishes from sibling tools like pbi_pages (listing pages) and pbi_fire_bookmark (bookmark navigation).

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?

Provides clear when-to-use context: navigation requiring exact name. Advises using pbi_wait_for when not blocking, and explains waitReady:true behavior for waiting on rendering. Does not explicitly contrast with alternatives but covers key scenarios.

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