kadam_adv_list_payment_systems

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

readOnlyHint=true already establishes the safe-read profile, and the description adds real behavioral context beyond it: the per-currency shape of the returned conditions and the filtering rule that administrator-reserved systems are excluded. It does not mention auth scope or pagination, but for a no-param read tool the added disclosure is meaningful.

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 compact sentences: what is returned, when to call it, and what is filtered out. Every clause carries information, and the primary purpose is front-loaded.

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?

With no output schema, the description compensates by naming the fields a caller will receive and the exclusion rule, so an agent knows both the trigger and the payload shape. Nothing needed to invoke this zero-arg read tool correctly is missing.

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?

The tool takes zero parameters, so there is nothing for the schema to describe and the baseline of 4 applies. The description correctly adds no parameter guidance because none is needed.

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 uses a specific verb ('Lists') and a precise resource ('the payment systems the account may deposit through'), then enumerates the returned fields (commission, min/max amount, exchange rate). No sibling tool covers payment systems, so the resource itself is self-distinguishing within the sibling set.

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 before advising on a deposit' gives an explicit triggering condition, which is more than most list tools provide. It stops short of naming any alternative or stating when-not-to-call, but the intended call site is unambiguous.

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