Sync Channel

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

Annotations indicate the tool is not read-only (readOnlyHint=false), not destructive (destructiveHint=false), and idempotent (idempotentHint=true). The description confirms it triggers a sync (a write operation) and returns status, but does not disclose additional behavioral traits such as authentication requirements, rate limits, or side effects beyond synchronization. It adds some value by explaining the two-way nature, but behavioral transparency is limited.

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 essential purpose. It includes both English and Spanish translations, which is slightly redundant but acceptable. Every sentence adds value; there is no fluff.

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 tool has 2 parameters, one required, an output schema exists, and annotations are provided, the description is complete. It explains the function, direction options, and return value summary. No additional information is necessary for correct invocation.

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 covers 100% of parameters with descriptions. The tool description adds meaning beyond the schema by explaining that direction options correspond to pulling reservations or pushing calendar updates. This clarifies the real-world effect of the enum values, which is helpful for selection.

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 triggers a manual sync of a booking channel, specifies the actions (pulling reservations and pushing calendar updates), and mentions the return type (sync status and counts). This is specific and distinct from sibling tools, which are mostly related to clients, invoices, or other entities.

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 what the tool does but does not provide explicit guidance on when to use it versus alternatives (e.g., automatic sync). No when-not or alternative tools are mentioned. The context of manual sync is implied but lacks explicit usage boundaries.

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