get_all_rates

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral nuance: NBP publishes rates only on banking days, so weekend dates return the most recent available table and the effective date is shown. This goes beyond the schema and helps the agent interpret 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 two concise sentences plus a compact Args block. It front-loads the core purpose and only adds necessary detail about the parameter. No redundant or filler content.

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 the tool's simplicity (one optional parameter, output schema available), the description is highly complete. It covers purpose, parameter semantics, and a real-world edge case. It does not list every currency or error handling, but that exceeds what's needed for selection and invocation.

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 schema has only a 'date' parameter with zero description coverage, so the description must compensate fully. It does: explains the ISO format, marks it optional, and describes what happens with weekend dates. This gives the agent everything needed to invoke the tool correctly.

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 the tool's function: 'Get all current PLN exchange rates from the National Bank of Poland' with specific scope (Table A, list of currencies). It differentiates from siblings like get_currency_rate, which likely returns a single rate, by emphasizing 'all' rates.

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 provides useful context (optional historical date, weekend behavior) but does not explicitly mention when to use this tool versus alternatives like get_currency_rate or convert_currency. The usage guidance is implied by the 'all' phrasing, not stated directly.

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