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

There are no annotations, so the description carries the full burden of disclosing behavioral traits. It only states what the tool returns, but does not explicitly confirm it is read-only, nor does it describe error handling or what happens if the customer or token does not exist. The word 'Get' implies non-mutation, but without annotations this is not sufficiently explicit.

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 starts with the verb 'Get' and immediately conveys the purpose. There is no filler or repetition, making it optimally sized and front-loaded.

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?

This is a simple tool with two clearly described parameters and no output schema, so the description's claim of returning 'balance and tier info' is minimally adequate. However, it lacks details on the response structure (e.g., what fields constitute 'tier info'), potential errors, and typical use cases, leaving gaps for a complete understanding.

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 input schema already provides descriptions for both parameters (token contract address, customer wallet) with 100% coverage. The tool description adds no additional meaning beyond the schema. Given the baseline of 3 for high schema coverage, this score is appropriate.

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 the action ('Get'), the resource ('loyalty token balance and tier info'), and the target ('for a customer'). It distinguishes itself from sibling tools like mint_loyalty_tokens or transfer_loyalty_tokens by being a read-only query, and the explicit mention of 'balance and tier info' makes it specific.

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 provides no guidance on when to use this tool versus alternatives. It does not mention that get_my_profile might be used for the caller's own balance, or that this tool is for querying a specific customer's balance given a token address. No prerequisites or exclusions are stated, leaving the agent to infer usage from the name alone.

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