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

With no annotations, the description carries the full behavioral burden. It mentions effect duration and requestId format, but does not disclose whether the potion is consumed, whether the action is reversible, what happens on failure, or why requestId is required.

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 two short, front-loaded sentences with no wasted wording. The core action and key constraints are presented immediately.

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 mutation tool with no annotations and no output schema, the description omits critical context: whether the potion is consumed, what the response contains, and what requestId protects against. It is too sparse for an agent to invoke with full confidence.

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 0%, so the description must compensate. It adds some meaning by saying potionId may be a potion ID or recipe ID and that requestId must be a UUID, but it does not explain requestId's purpose or resolve the mismatch between 'recipe ID' and the single potionId parameter.

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 states a specific verb and resource: 'Drink a potion you own,' with optional identification methods. It is clear enough to distinguish from brewing or gifting, but it does not explicitly differentiate from siblings like consume or gift_potion.

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?

It implies usage by saying the potion must be owned and that effects last one hour, but it gives no explicit when-to-use guidance, prerequisites beyond ownership, or alternatives such as consume or gift_potion.

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