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

Annotations already declare readOnlyIdempotent/non-destructive, so safety is covered. The description adds genuinely useful context beyond them: the free-check quota is 5 per day and is shared with quelta.ai, which explains cross-product consumption behavior an agent could not infer elsewhere.

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?

A single front-loaded sentence naming the resource first, then the fields, with a compact parenthetical that carries real information (the 5/day shared quota). Nothing is padded.

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 read with no output schema, the description covers the key returned fields and the quota rule. Minor gaps remain about the units/meaning of 'full checks on the balance', but the core is complete.

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 takes no parameters, so per the baseline there is nothing for the description to disambiguate; the description sensibly spends its words on returned data instead.

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 (Show) and resource (the connected Quelta account) and enumerates exactly what is returned: email, free preliminary checks left today, and full checks on the balance. The resource is clearly distinct from the sibling tools (analyses, video ads, upgrades), though no sibling is named explicitly.

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?

Usage is only implied: an agent can infer this is the tool for checking account status and remaining quota balances. There is no explicit when-to-use statement and no guidance on when another sibling (e.g. upgrade_to_full_review) is the better call after seeing the balance.

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