safari_read_tab

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

The description does not disclose what 'content' entails (e.g., visible text, HTML source, dynamic content), whether it requires accessibility permissions, or if it reads from the active tab only. Without annotations, the description carries the full burden but provides minimal behavioral detail.

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 short phrase with no unnecessary words. It is front-loaded and efficient, earning its place without any fluff.

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 absence of an output schema and parameters, the description lacks completeness about what is returned (e.g., text format, limitations) and how the tool selects a tab. More context about the behavior would improve usability.

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?

There are no parameters (0), and the schema coverage is 100%, so the description naturally adds no parameter details. According to the calibration rule, 0 parameters warrants a baseline score of 4. The description does not detract from this but also does not add implicit parameter semantics like 'reads the currently active tab.'

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 verb 'read' and the resource 'content of a Safari tab'. However, it does not specify which tab (e.g., active tab or by identifier), which could cause ambiguity. The name and description together differentiate it from sibling tools like safari_search_tabs and safari_click.

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 on when to use this tool versus alternatives like safari_search_tabs or list_safari_bookmarks. The description lacks explicit context about prerequisites or typical use cases.

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