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

While annotations already declare this is a read-only, non-destructive operation, the description adds behavioral context by including the API endpoint structure (GET /lists/{uuid}/subscribers/{id}/rewards), which clarifies its technical implementation.

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 highly efficient. It front-loads the core purpose, adds critical usage context, and includes the technical path in just two focused sentences.

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?

The description provides more than just a list of fields; it explains the utility of the data (linking reward IDs to update functions) and provides the API path. This provides a complete picture for agent invocation.

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?

Given that the schema coverage is 100%, the description meets the baseline expectation for parameter clarity. It reiterates the necessary contextual fields like 'status' and 'value' to reinforce the data returned.

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 it lists rewards for 'one subscriber,' which immediately differentiates it from sibling tools that might list rewards for an entire campaign or organization.

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 provides valuable usage context by explicitly linking the 'reward id' returned by this tool to a dependency in the write operation, `referralhero_update_reward_status`. This guides the agent on the tool's role in a workflow.

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