loyalteez_list_perks

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

No annotations are provided, so the description must carry the behavioral burden. It discloses that this is a read-style 'Get' operation and that the response includes perk details, pricing, and availability, but it omits auth requirements, pagination behavior, rate limits, and whether it is strictly read-only.

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 definition is front-loaded, with the core action in the first sentence and return contents immediately after. The doc link is compact and does not bury the essential information.

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 read-only list tool with four fully documented parameters, the description gives a useful high-level return summary and points to additional docs. It still lacks output schema detail and does not cover pagination, but the schema and doc reference make it mostly 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?

Schema description coverage is 100%, so all four parameters are already documented in the input schema. The description adds no parameter-level filtering, default, or formatting semantics beyond what the schema provides, making 3 the appropriate baseline.

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: get/list all available perks, with clarifying parenthetical NFT rewards. It distinguishes itself implicitly from redeem_perk and check_perk_eligibility, but it does not explicitly name or contrast with those siblings.

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 implies usage by saying these are perks users can claim with LTZ balance, suggesting it is a discovery/listing step before claiming. However, it gives no explicit when-to-use guidance, no prerequisites, and no comparison to alternatives like check_perk_eligibility or redeem_perk.

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