investor_sync_data

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

No annotations are provided, so the description carries full burden. It states 'Read-only in MVP', which suggests no side effects, but this is somewhat contradictory for a sync tool. No details on what data is affected, whether it triggers background jobs, or authorization needs.

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 short and front-loaded with the core action. However, the second sentence could be integrated or elaborated, but overall it is not verbose.

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 lack of annotations, output schema, and parameter descriptions, the description is incomplete. It does not explain return values, sync behavior (incremental vs full), or how the 'force' or date parameters work. The read-only claim adds confusion without resolution.

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?

The input schema has 5 parameters with 0% description coverage, and the tool description provides no explanations for 'mode', 'account_ids', 'force', 'from_date', or 'to_date'. The agent cannot infer their meanings or constraints from the description 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 tool synchronizes broker and market data, which is a specific verb+resource. The 'Read-only in MVP' qualifier adds constraint but doesn't cloud the primary action. It distinguishes from sibling tools like investor_get_sync_status which likely only retrieves status.

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 is given on when to use this tool versus alternatives like investor_get_sync_status or investor_get_portfolio. There is no mention of prerequisites or contexts where syncing is appropriate.

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