integration_sync

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

With no annotations, the description discloses key behaviors: idempotent operation, auto-mapping of labels (e.g., 'priority:high'), and that it creates 'kagan tasks'. It does not detail authentication, rate limits, or side effects, but the idempotency hint mitigates concerns.

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 concise with a brief summary followed by an Args list. Every sentence is informative, no redundant content. It is well-structured and easy to parse.

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 6 parameters and the presence of an output schema, the description covers the purpose, behavior, and all parameter details effectively. It explains the auto-mapping feature and idempotency, providing a complete picture.

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?

All 6 parameters are described in the Args section, adding meaning beyond the input schema (e.g., 'repo' expects owner/repo format, 'state' defaults to 'open', 'labels' are AND filters). Schema description coverage is 0%, so the description fully compensates.

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 syncs external items (issues) from an integration source into the active project as tasks. It uses specific verbs and resources, and distinguishes itself from siblings like integration_preflight and integration_preview.

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 idempotency (skipping previously synced issues) and details parameter use (e.g., state filter, labels, limit). However, it does not explicitly contrast with alternative tools or state when not to use this tool.

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