intelligence_sync

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the agent knows this reaches external sources and mutates local state without being destructive. The description usefully adds that it updates a local cache and reports per-source failures plus scope, but omits whether the sync is blocking, whether it overwrites existing cached advisories, and any auth or rate-limit constraints.

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?

Two short sentences with no filler, and the primary action is front-loaded ahead of the return-value note. It is efficient, though 'scope' is left unexplained and reads as an afterthought.

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 restated, and the description does gesture at per-source failures. However, for a non-read-only tool with an open-world dependency and two completely undocumented parameters, the definition leaves too much unstated to call it complete.

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 neither of the two parameters is described in the schema. The description never mentions 'limit' or 'sources', so an agent gets no help understanding what limit bounds or what source identifiers are valid — a real gap for a tool whose only inputs are these two fields.

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?

States a specific verb pair (fetch + update local cache) and a concrete resource (official public mobile advisories), which separates it from read-only siblings like intelligence_get and intelligence_search. It stops short of explicitly naming those siblings as the non-sync alternatives, so it is clear but not fully differentiated.

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 run a sync versus calling intelligence_search or intelligence_get directly, no mention of prerequisites, freshness needs, or how often it should be invoked. The agent must infer the trigger condition entirely from the name.

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