ghl_payments_currency_get

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Get' implies a read-only operation, but the description reveals nothing about authentication requirements, rate limits, response behavior, or error conditions. This is severely under-specified even for a simple retrieval operation.

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 exactly three words: 'Get payment currencies'. It is maximally concise and front-loaded, with every word contributing to conveying the tool's purpose. There is zero wasted text, which is ideal for a tool with no parameters and trivial invocation.

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?

While the tool's complexity is low (no parameters, no output schema), the description still feels incomplete in terms of context. It does not explain what 'payment currencies' are, what the response will look like, or why a caller might want this data. However, given the simplicity and obvious use case, the minimal description is borderline acceptable, meriting a middle score.

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 has zero parameters, and the schema confirms this with no properties. Per the rubric, zero parameters warrant a baseline of 4. The description adds no parameter-level detail because none exist, and no additional semantic explanation 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 'Get payment currencies' uses a specific verb ('get') and clearly identifies the resource ('payment currencies'). It distinguishes the tool from all siblings, none of which reference payments or currencies, making it unambiguous among the provided tools.

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?

There is no guidance on when to use this tool or any comparison to alternatives. The description offers no context about prerequisites, execution conditions, or when it would be preferred over other tools, so the agent receives no explicit usage direction.

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