safari_read_tab

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'Read content', implying a non-destructive read, but does not specify which tab is read (e.g., active tab), what happens if no tabs are open, required permissions, or whether the operation is synchronous. This is insufficient for an agent to understand 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 of five words, which is extremely concise and front-loaded. Every word earns its place, and there is no redundancy. For a no-parameter tool, this is appropriately sized.

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 and the tool's complexity (reading a tab's content), the description lacks important context: which tab (active? by URL?), what format is returned (text, HTML?), and whether the tool is limited to certain tab types. The agent has insufficient information to use the tool correctly.

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 the baseline is 4. The description does not add parameter information because none exist. This is adequate given that no parameters need documenting.

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 'Read' and the resource 'content of a Safari tab'. It distinguishes from sibling tools like safari_click (interaction) and safari_search_tabs (searching tabs). However, it could be more specific about what 'content' means (e.g., HTML, text, or rendered content).

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 no guidance on when to use this tool versus alternatives such as safari_search_tabs or safari_click. It does not mention prerequisites, limitations, or context for its use. A clear usage scenario is missing.

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