monobank-bank-currency

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so safety profile is covered. The description adds valuable field-level behavior: conditional presence of rateSell/rateBuy versus rateCross, and the ISO 4217 explanation, which goes beyond annotations.

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 structured as a concise intro followed by a bulleted list of response fields. Each line is informative and necessary, avoiding tangents. It is slightly longer than minimal but earns its length by clarifying field semantics.

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 there is no output schema, the description fully compensates by documenting all response fields, including conditional presence and meaning. For a zero-param read-only tool, this is complete and self-sufficient; the agent can confidently invoke it and interpret results.

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, so the baseline is 4 per the rubric. The description adds no parameter semantics because none exist; it appropriately focuses on response fields instead. Schema coverage is trivially 100% with an empty schema.

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 opens with 'Returns Monobank exchange rates for all supported currencies,' providing a specific verb, resource, and scope. This clearly distinguishes it from sibling 'monobank-bank-currency-rate' which likely targets a single rate or pair.

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 explicit guidance on when to use this tool versus the sibling 'monobank-bank-currency-rate'. The description implies broad coverage ('all supported currencies') but does not state exclusions or alternative conditions, leaving the agent to infer usage.

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