research_sync

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

With no annotations, the description carries the full burden of disclosing side effects. It states actions like 'import' and 'export' but does not clarify whether these modify data, require specific permissions, or have other behavioral implications. The phrase 'optionally audit' is undefined, leaving the tool's behavior largely opaque.

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 sentence, which is concise, but its structure is disjointed—listing three actions without clear separation or emphasis. The phrase 'and optionally' adds confusion about whether audit is a separate mode or a modifier. It is not well-organized given the multi-part functionality.

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 an output schema exists, the description does not explain how the tool's multiple modes are invoked or what inputs are required for each. For a tool with two primary directions (import/export) and an audit option, the description omits critical context about parameter combinations and expected outcomes, leaving it incomplete.

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%, so the description must compensate for the four undocumented parameters. It loosely maps to parameters (events, project, packet_id, used_record_ids) but does not explain their formats, defaults, or how they control the import/export/audit modes. This is insufficient for a 4-parameter tool.

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 lists three actions: import events, export project events, and optionally audit packet records. While each action has a verb and resource, the overall purpose is vague because it's unclear how these actions relate or when each is intended to be performed. It does not clearly distinguish itself from sibling tools beyond the name 'sync'.

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 use this tool versus alternatives. The description does not mention any prerequisites, exclusions, or comparisons to sibling tools like research_query or research_validate. Users are left to infer usage context on their own.

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