sync_organization_events

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

With no annotations, the description must carry behavioral disclosure. It mentions writing to SQLite and the two sync modes, but does not disclose potential side effects such as whether existing data is deleted during a full backfill, whether the operation is destructive, or what happens to events removed from Eventbrite. This is a significant gap for a mutation tool.

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 two sentences long, front-loaded with the primary purpose, and contains no filler. The mention of 'changed_desc' is cryptic but does not detract from conciseness.

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 tool has an output schema (not shown) and two parameters. The description explains the overall sync behavior but omits details about the return value (though output schema covers that), prerequisites, error handling, and the meaning of 'changed_desc'. For a tool that writes to a database, more context on side effects and idempotency would be needed.

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 does not mention the parameters at all. The schema provides only titles and types for organization_id and force_full_resync, but no explanatory text. The description does not compensate for this gap, leaving the agent to infer parameter meaning from names alone.

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 (synchronize), the resource (events from Eventbrite API), and the destination (local SQLite database). It also distinguishes between full backfill and incremental delta sync, making it distinct from read-only list/search siblings.

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 explains the two operating modes (full backfill when new, incremental delta via 'changed_desc'), which guides when the tool performs full vs. incremental work. However, it does not explicitly mention alternatives or exclusions (e.g., 'use list_organization_events for read-only queries'). The context is clear enough for a sync tool, but not fully explicit.

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