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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds value by listing what comes back (wallet addresses, voucher stats, balances, tier info), but says nothing about export volume, pagination, rate limits, or any auth/sensitivity requirements for bulk customer address data — the kind of context that matters for an export.

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?

Three short sentences, front-loaded with the action and scope, then the return contents, then the use case. No filler, though the trailing 'analytics, segmentation, personalized offers' list is somewhat generic boilerplate rather than actionable guidance.

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 one-parameter read-only export with a fully-covered schema and no output schema, the description covers action, scope, and the shape of returned data. The only meaningful gap is behavior at scale (pagination/limits) and the absence of any sibling disambiguation, which keeps it from being fully 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% and there is a single required parameter, so the schema already does the work. The description only implies that 'token_address' identifies the loyalty program ('for a specific loyalty program') and adds no format, validation, or lookup-hint detail beyond that. Baseline 3 is correct.

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+resource with scope: 'Export customer data for a specific loyalty program', and enumerates the payload (wallet addresses, voucher stats, balances, tier info). Clear on its own, but it never contrasts itself with a close sibling like get_program_analytics, so the agent must infer the boundary between customer-level export and program-level analytics.

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?

'Use for analytics, segmentation, and personalized offers' gives implied usage context, but does not say when NOT to use it or name an alternative (e.g. get_program_analytics for aggregate metrics, create_personalized_offer for the follow-up action). The agent gets a use case, not a routing rule.

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