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

Annotations already mark this as readOnly and non-destructive, but the description goes further by explaining the semantics of credits and generations_remaining, including that credits are a shared balance, publishing uses one credit, extra phone-guest batches use additional credits, and generations_remaining does not reset over time. This is valuable behavioral context beyond the annotations.

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?

Every sentence earns its place: trigger conditions, credit semantics, generation semantics, the credit-to-generation conversion, and related tool routing. The most important usage guidance is front-loaded, and there is no filler or repetition.

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 account status tool with an output schema, the description is complete. It explains both key output fields, their relationship, non-resetting behavior, and related tools for actions like adding credits or checking invitation requirements. No important context 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 and 100% schema description coverage, so the baseline is 4. The description adds meaning to the output fields (credits and generations_remaining) rather than input parameters, which is appropriate for a zero-parameter read-only account tool.

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 explicit trigger conditions: which account is connected, how many credits it has, or how many design generations are left. It names the resource (Lemonvite account) and the specific fields, clearly distinguishing it from generation, invitation, and checkout tools.

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 gives explicit when-to-use guidance and points to alternatives: lemonvite_start_checkout for adding credits and lemonvite_get_invitation for invitation-specific required_credits. It also clarifies how generations_remaining relates to lemonvite_generate_design and lemonvite_edit_design, so an agent can route correctly.

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