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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds value the annotations don't: only *active* currencies are returned, and all monetary amounts in the system are denominated in USD, which is important interpretation context for downstream calls.

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?

Two short sentences, front-loaded with what is returned and followed by the USD basis. Nothing is padded or redundant.

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?

For a trivial no-param lookup with no output schema, the description covers scope (active only) and the meaning of the numeric values (USD rates). The only minor gap is the exact field shape of each currency entry, which an agent must discover from the response itself.

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 no parameters, which is the baseline-4 case. The description correctly doesn't invent parameter semantics, and the zero-parameter nature is consistent with the 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?

States the resource (currencies) with a scope qualifier (active) and the payload each carries (USD rates), so an agent knows exactly what comes back. It doesn't explicitly say 'list' or name a sibling, but no sibling in the list could be confused with a currency catalogue.

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?

Usage is only implied – an agent infers it should call this when it needs the set of active currencies or a USD conversion factor. There are no exclusions or prerequisites, though with zero parameters and no competing tool there is little to disambiguate.

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