chrome_read_tab

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

With no annotations, the description must disclose behavioral traits. It adds the nuance of 'rendered text content' (vs. HTML source), which is helpful. However, it does not explicitly confirm it is read-only, mention error states (e.g., no open tab), or describe any side effects. It provides minimal but not insufficient transparency.

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 concise and front-loaded. Every word contributes to the purpose. No filler or repetition.

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 tool has no output schema, no annotations, and many sibling tools, the description is incomplete. It does not specify which tab is read, the output format, or error handling. The agent lacks context to fully understand the tool's behavior and limitations.

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 input schema has zero parameters, so schema coverage is 100%. With no parameters to document, the description does not need to add parameter-level information. Baseline score for 0 parameters is 4, and the description does not contradict or miss any param details.

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 ('reads') and the resource ('rendered text content of a Google Chrome tab'). It distinguishes from sibling tools like chrome_click or chrome_navigate, but does not specify which tab is read (e.g., the active tab). This leaves minor ambiguity but overall purpose is clear.

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 this tool versus alternatives like safari_read_tab or chrome_query_selector_all. There is no mention of prerequisites, context, or exclusions. The description merely states what it does without helping the agent decide when to invoke it.

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