shared_lists_sync

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

Annotations already state readOnlyHint=false and destructiveHint=false, so the agent knows this is a non-destructive mutation. The description adds real behavioral context: it pushes every plugin referencing the list to the nodes where it is active, implying a fan-out write across nodes. It does not disclose idempotency, required permissions, or rate/scope limits.

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, front-loaded with the verb+resource. No wasted words. The second sentence earns its place by describing the propagation effect.

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 single-param mutation with no output schema, the description covers what happens but omits what is returned or how to verify the sync, and gives no usage context. Adequate but with clear gaps.

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 coverage is 0%, but there is only one parameter and the schema still enforces its format via pattern/length. The description implicitly identifies 'name' as the shared list identifier ('this shared list'), which is minimal but adequate for a single-param tool.

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 (sync) and resource (Shared List) plus the propagation target (nodes). The second sentence clarifies the actual effect, distinguishing it from a plain update. It does not explicitly contrast with the closely-named sibling shared_lists_update, so it falls short of a 5.

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?

There is no explicit when-to-use guidance, no prerequisites, and no mention of the alternative shared_lists_update or node_plugins_sync. The description explains the mechanism of syncing rather than when an agent should choose this tool over siblings.

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