diana_community_sync

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

Annotations only declare openWorldHint and idempotentHint, and the description adds substantive behavior beyond them: the source content is Markdown-only, no contributed executable code is ever run, and there is no hidden startup synchronization. The remaining gap is what an update does to locally modified or existing copies, which the idempotent hint only partially covers.

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?

Three short sentences, front-loaded with the action and followed by the safety and consent facts the agent most needs. Sentence content earns its place, though the leading adverb 'Explicitly' is slightly awkward and the consent-boundary point is restated implicitly by the no-hidden-sync sentence.

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?

An output schema exists, so return values need not be explained, and the description covers the security, network-consent and optionality concerns that matter for this operation. It would be stronger if it pointed at the preview/status siblings for the 'what will I get' and 'is a sync already done' questions.

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 tool takes zero parameters, so there is no parameter meaning for the description to add; the baseline for a parameterless tool applies. Nothing is missing on this dimension.

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 names a specific verb pair (download/update) and a specific resource (the optional public community experience repository), so the agent knows exactly what the tool acts on. It does not explicitly contrast itself with the closely related siblings diana_community_preview, diana_community_status or diana_community_prepare, leaving the agent to infer the division of labor from the names alone.

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 wording 'Explicitly ... the network-consent boundary' and 'optional' implies the tool is used only when the user wants network access triggered, which is real conditional guidance. However, no sibling is named as an alternative, and there is no statement of when-not to call it (e.g. 'use preview first to inspect contents' or 'check status before syncing').

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