ramzinex_get_commissions

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

No annotations are provided, so the description carries the full burden. It correctly states 'read-only' but lacks details on error handling, rate limits, or data freshness. The credentials requirement is noted, but overall behavioral context is minimal.

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 verbose with technical notes about the Postman collection, URL assumption, and Persian text. This extraneous information reduces clarity and efficiency for an AI agent.

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?

An output schema exists, so return values are covered. The description adequately explains the tool's purpose and the single parameter. However, the 'best-effort' caveat introduces uncertainty, and no guidance on when to use relative to sibling tools is provided.

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?

With only one parameter (instance) and 0% schema coverage, the description adds value by explaining 'Configured instance to use (default when omitted)'. This compensates well for the lack of schema documentation.

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 'List commission / fee history (read-only)' which specifies the verb and resource. The Persian translation reinforces the purpose. Among siblings like ramzinex_get_rewards and ramzinex_get_turnover, this tool is distinctly about commissions/fees.

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' but does not specify when to use this tool over alternatives like ramzinex_get_rewards. The 'BEST-EFFORT PATH' note implies uncertainty, which undermines clear guidance.

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