zernio_get_single_account_health

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

The description clearly explains the tool's purpose (checking auth token validity) and implies it is a read-only operation. With no annotations, the description transparently conveys the behavior. No mention of side effects or error cases, but it's sufficiently clear for a simple check.

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 a single, concise sentence that front-loads the key information. No redundant wording.

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?

Given the tool's simplicity (1 parameter, no output schema), the description is complete. It covers the tool's purpose and the key aspect of auth token validation, sufficient for an agent to understand and invoke it correctly.

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% for the single parameter 'accountId'. The description adds meaning by explaining it checks a 'specific social account' and focuses on 'auth token' validity, providing value beyond the schema's parameter description.

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 clearly states it checks the health/connection status of a specific social account by ID, using a specific verb ('check') and resource ('health/connection status'). It distinguishes itself from the sibling 'zernio_get_account_health' by specifying 'single account'.

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 explicit guidance on when to use this tool versus the sibling 'zernio_get_account_health'. The differentiation is implied by the name 'single', but without explicit context or exclusion, the agent must infer.

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