live_browser_load

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

No annotations are provided, so the description carries the full burden. It only states the core action without disclosing behavioral traits such as whether the operation is read-only, mutates state, requires authentication, or has side effects. For a tool that likely retrieves and loads an item, the lack of any safety or behavioral context is a gap.

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 that is front-loaded and contains no extraneous information. It is as concise as possible while conveying the essential purpose.

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 complexity of 4 parameters (including nested objects) and no output schema, the description is too sparse. It fails to explain what 'loading' entails (e.g., does it return the item? modify state?), the role of target_track, or the meaning of expected_set_signature. The agent lacks enough context to use the tool correctly without additional assumptions.

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 low (25%), and the description adds minimal value beyond what is already in the schema. It clarifies that the 'item' parameter accepts id, uri, or path, but offers no explanation for the other three parameters (target_track, timeout, expected_set_signature). The description does not compensate for the low coverage of undocumented parameters.

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 'Load' and the resource 'BrowserItem' with explicit search criteria (by id, uri, or path). It distinguishes from siblings like live_browser_search (which lists items) and live_browser_preview (which likely provides a preview), as loading indicates a retrieval operation.

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 that the tool is used after a browser search by mentioning 'from search', but it does not explicitly state when to use this tool versus alternatives (e.g., live_browser_preview) or provide exclusions. It offers no guidance on prerequisites or common scenarios.

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