Check LipDub connection

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

Annotations already declare readOnly, idempotent, and non-destructive, but the description goes further: it states that the tool does not use credits and does not start anything, and it discloses that credit balance is not available via the API, directing users to the web app. These are behavioral details beyond what annotations capture, providing real value for an agent deciding whether to call it.

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 three short paragraphs, each with a distinct purpose: purpose, when to use, and notes. Every sentence earns its place with no filler. The key purpose is front-loaded, and the caveats are placed last without bloating the text.

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 zero-parameter health-check tool with no output schema, the description fully covers what an agent needs: what it does, when to use it, what it doesn't affect, and an important limitation (credit balance). The sibling tools are all about renders, so this check tool is clearly distinct. Nothing essential 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?

The tool has zero parameters, so there is nothing to describe. The schema coverage is trivially 100%. Per the baseline rule, a score of 4 is appropriate because the description adds no parameter-specific info, but none is needed. The description correctly avoids inventing unnecessary parameter explanations.

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 opens with a concrete verb+resource: 'Verify that this server can reach LipDub and report which account it is using.' This is unambiguous and clearly distinguishes it from the sibling render-management tools. Even without seeing the siblings, the tool's role is immediately understandable.

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?

Explicitly states when to call it: 'Call this first if any other LipDub tool fails with an authentication error, or when a user asks whether LipDub is set up.' It also clarifies what it does NOT do (uses credits, starts anything), which prevents misuse. This is textbook usage guidance.

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