sync_sms_history

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

With no annotations, the description must carry the behavioral burden. It usefully discloses that the data comes from the mobile cache and is redacted before ingestion, but it does not state whether ingestion mutates local storage, whether an active pairing is required, or what effects repeated calls have.

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 one short sentence with no filler, and the core action is up front. It loses a point only for the slightly awkward grammar and for not using the available space to clarify the parameter.

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?

Although the tool is simple and has an output schema, the description omits usage guidance, side effects, and the meaning of wait_seconds. An agent can identify the operation but not confidently pick or invoke it among the sibling tools.

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?

Schema description coverage is 0% and the description never mentions wait_seconds. The only parameter's meaning must be inferred from its name and default, and the description adds no clarification about what waiting applies to.

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 names a concrete action: it asks the phone for cached conversations and ingests them redacted. This clearly maps to the tool name and distinguishes it from generic getters, though it does not explicitly contrast it with sibling tools like get_conversation.

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?

There is no guidance on when to call this tool versus siblings such as get_conversation or list_active_notifications, and no mention of pairing or prerequisites. The intended use is only weakly implied by the tool name.

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