ramzinex_get_rewards

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

With no annotations, the description fully handles behavioral disclosure. It declares the operation as read-only, notes required credentials, and transparently explains that the endpoint is a best-effort assumption based on documentation gaps. This goes beyond minimal disclosure.

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 multi-line but well-structured: clear purpose, Persian translation for locale, prerequisite note, implementation uncertainty disclosure, and parameter explanation. Each sentence adds value without being verbose.

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?

Given the tool's simplicity (one optional parameter) and the presence of an output schema (which covers return structure), the description adequately covers context: read-only nature, credential requirements, and implementation status. It is sufficient for an agent to use correctly.

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 coverage is 0%, so description must compensate. The single parameter 'instance' is described as 'Configured instance to use (default when omitted)', which adds the concept of a default behavior beyond the schema. However, it does not explain what an 'instance' is or how it affects the request, leaving some ambiguity.

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 'List reward / cashback entries (read-only)', which is a specific verb+resource. Among many sibling get_* tools, this is the only one for rewards, so it distinguishes clearly.

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 mentions 'Requires configured credentials' as a prerequisite, but does not provide guidance on when to use this tool versus alternatives or when not to use it. Usage context is implied but not explicit.

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