safari_history

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

With no annotations provided, the description carries full burden and discloses read-only behavior, no page opening, and local SQLite storage. It lacks details on output format or performance, but adequately covers safety and data source.

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?

Single sentence with immediate purpose, followed by parenthetical detail. No unnecessary words, front-loaded and efficient.

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?

The description mentions 'lists or searches' but the schema has no parameters, creating potential confusion about how searching is performed. Given the absence of an output schema and the many sibling tools, this ambiguity weakens completeness.

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?

No parameters exist, so baseline is 4. The description adds meaning by explaining the tool's purpose beyond the empty schema, though there is no parameter detail to add.

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 tool lists or searches Safari browsing history, specifies it reads local SQLite, is read-only, and does not open pages, effectively differentiating it from sibling tools like chrome_history and safari_navigate.

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 use for accessing Safari history, but does not explicitly mention when not to use or alternative tools. However, the context is clear enough for an AI agent to infer appropriate usage among Safari and Chrome tools.

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