tdarr_updater_check

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

No annotations are provided, and the description does not disclose behavioral traits such as side effects (e.g., downloading or applying an update). The paramaters hint at mutations, but the description claims only a check operation, which is inconsistent.

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 very concise (one sentence), but it is under-specified given the three boolean parameters. It front-loads the purpose but lacks necessary detail, making it more inadequate than concise.

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?

There is no output schema, and the description does not explain what the tool returns or what behaviors (like downloading or applying) are triggered by the parameters. Given the three parameters and the lack of annotations, the description is incomplete and fails to cover the tool's full scope.

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?

Although the input schema has 100% description coverage, the tool's description ('Check if an update is available') adds no value beyond the schema's parameter descriptions. In fact, it contradicts the schema by implying a readonly check while parameters allow actions, providing no clarity on when each parameter should be used.

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 'Check if an update is available' clearly states the tool's primary function, distinguishing it from sibling updater tools like tdarr_updater_package_index and tdarr_updater_relaunch. However, the inclusion of paramaters like downloadUpdate and applyUpdate suggests broader functionality, creating slight ambiguity.

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 provides no guidance on when to use this tool vs alternatives (e.g., tdarr_updater_package_index) or any prerequisites. There is no explanation of the required boolean parameters or when it's appropriate to set them to true/false.

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