update_community_plugins

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

With no annotations, the description carries the full behavioral disclosure burden. It explicitly warns that Community plugins are overwritten and that Local plugins are unaffected, which are the key behavioral traits beyond the action itself. It does not detail irreversibility or side effects beyond the overwrite warning, but the warning is sufficient for this tool's risk profile.

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 sentences with no filler. The action and endpoint are front-loaded, and the critical overwrite warning is placed immediately after, making the description scannable and efficient.

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 simple one-optional-parameter tool with no output schema, the description provides everything an agent needs to invoke it correctly: the purpose, the scope, the endpoint, and the destructive overwrite warning. No critical calling information is missing.

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 100%, so the schema fully documents the 'force' parameter. The description adds no additional detail about the parameter beyond what the schema already provides, so the baseline score of 3 applies.

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 action ('Pull the latest Community plugins'), a specific resource ('Tdarr plugin repo'), and the exact endpoint. It distinguishes itself from sibling plugin tools by stating it operates on all Community plugins and leaves Local plugins untouched.

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 makes the scope clear: use this tool to update Community plugins from the Tdarr repo. The statement that Local plugins are untouched provides an exclusion, though it does not explicitly name alternative tools such as copy_community_plugin_to_local or sync_plugins_to_nodes.

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