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

The description adds useful behavioral context by stating a rate limit of up to 6 times per hour and that the tool returns changes. The annotations already declare destructiveHint=true and idempotentHint=false, but the description does not explain what destructive side effects may occur during a sync, which is a notable 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 a single front-loaded sentence containing the action, rate limit, and outcome. It is efficient, though the phrase 'get what changed' is slightly vague.

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?

For a simple one-parameter tool with annotations covering destructive and idempotency behavior, the description is adequate but incomplete. It does not explain what 'what changed' means as a return value or warn about possible destructive effects, which matters given destructiveHint=true and no output schema.

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?

There is only one required parameter, and the schema already documents it as 'Integration id' at 100% coverage. The description does not add format or selection guidance beyond what the schema provides, so the baseline score of 3 is appropriate.

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 states a specific verb and resource: 'Sync a connected tool now'. It also says the result is 'what changed', which clarifies the immediate sync operation. It is clear, but it does not explicitly distinguish this from siblings such as get_integration, list_integrations, or connect_integration.

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 phrase 'now' and the rate limit imply this is for triggering an immediate sync rather than viewing integration details. However, there is no explicit when-not guidance and no named alternative for checking status or listing integrations.

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