get_fiat_deposits

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

No annotations are provided; the description only states 'Get' which suggests a read operation but offers no details on rate limits, authentication, or behavior with empty results.

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 very short and front-loaded with the main purpose. Parameter descriptions are listed clearly, with no wasted words.

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 tool has optional parameters and an output schema exists (not shown), but the description does not mention return value, pagination behavior, or edge cases. It covers basic semantics but is incomplete for a history-listing tool.

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 the description must compensate. It explains offset, limit, and from_date with brief specifications (e.g., 'up to 1000', 'YYYY-MM-DD'), but lacks details like starting offset or inclusivity of dates.

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 'Get fiat (AED) deposit history' with a specific verb and resource, and distinguishes from sibling tools like get_fiat_deposit (singular) and get_fiat_withdrawals.

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?

No guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. The parameter descriptions imply pagination but do not provide explicit usage context.

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