rr_trigger_sync

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

With no annotations provided, the description carries full burden. It only says 'trigger' but does not disclose any behavioral traits such as side effects (e.g., data overwrite, latency), required permissions, or what happens after triggering. This is a significant gap.

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 extremely short (4 words), but this is underspecification rather than conciseness. It earns its place but does not add sufficient value for the number of parameters and lack of annotations.

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 2 parameters (one required), no output schema, and no annotations, the description is completely inadequate. It does not explain what a sync entails, how to check progress, error cases, or any follow-up actions.

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 adds no meaning to the parameters. It does not explain the purpose of 'connector_type' enum values or 'store_id', nor how they affect the sync operation.

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 'Trigger an inventory sync' states a verb and resource, but it lacks specificity about what is synced or the scope. Without further detail, it is minimally adequate but could be confused with other sync-related tools like 'rr_get_sync_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 on when to use this tool versus alternatives such as 'rr_get_sync_status' or other inventory tools. There is no mention of prerequisites, conditions, or when not to trigger a sync.

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