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

With no annotations, the description carries the full burden. It implies a mutation (creating a tab) but does not disclose side effects, permission requirements, reversibility, or the response shape. The guest_token parameter is not even mentioned, so the agent cannot anticipate the authentication requirement.

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?

A single, front-loaded sentence with no wasted words. It is appropriately concise for the action, though it could be slightly more informative without losing brevity. The structure is clear and easily parsed.

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 no output schema, no annotations, and a minimal description, the tool is under-documented. The agent lacks information about expected outcomes, error conditions, or how the guest_token affects behavior. For a tool that creates a resource, this is insufficient.

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 only mentions 'URL' and adds nothing beyond the schema for url and alias. The guest_token has no schema description and is not explained here, so the description fails to compensate for the 67% schema coverage gap. It adds minimal semantic value.

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 states a specific action ('Opens a tab for a URL') and the resource (tab) and target (URL). It is clear and distinguishes from siblings like list_tabs or run_tab, though it does not explicitly name alternatives. The core purpose is unambiguous, but it could mention the guest_token requirement for completeness.

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. It does not mention prerequisites (e.g., guest_token) or when to prefer run_tab or list_tabs. The agent is left to infer usage context from the name and schema.

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