browser_reload

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

With no annotations provided, the description bears full responsibility for behavioral disclosure. It explains the effect (reloads a tab) and the optional bypass-cache behavior. However, it does not mention whether unsaved form data is lost, whether pending downloads are interrupted, or if any permissions are needed. It covers the core action but lacks depth on side effects.

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 9 words, with no filler. Every word serves a purpose: 'reload' (action), 'one explicitly shared exact tab' (scope), 'optionally bypassing cache' (modifier). This is exemplary conciseness.

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 zero schema coverage, no annotations, and a simple 2-parameter tool, the description provides a minimal viable specification. It explains what the tool does and the optional behavior, but lacks parameter-level detail for the required collaboration_id and does not explain the return value (since no output schema). It is sufficient for a simple tool but not rich.

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 0%, so the description must compensate. It mentions 'bypassing cache' implicitly for ignore_cache, but does not explain how the bypass works or the implications. The required parameter collaboration_id is not explained at all – the agent must infer its meaning (identifying the tab to reload) from context. This is a moderate gap.

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 states the action ('reload'), the target ('one explicitly shared exact tab'), and the optional modifier ('bypass cache'). This unequivocally distinguishes the tool from siblings like browser_navigate (which changes URL) and browser_open (which opens new tabs).

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 provides clear context for when to use it ('reload an explicitly shared exact tab'). However, it does not provide explicit exclusions or direct comparison to alternatives, such as when to use browser_navigate with the same URL versus reload, or when to use ignore_cache. This leaves some ambiguity for the agent.

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