concur_list_currencies

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description confirms the list is of accepted currencies and returns code+name, but says nothing about ordering, result size, or the fact that view="raw" returns unprojected upstream data beyond what the schema states.

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?

One front-loaded sentence with no filler; the resource and the optional filter are stated in the first clause.

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 simple, read-only, zero-required-parameter lookup with full schema coverage, no output schema, and annotations covering safety, the description supplies what is needed to call it. A note on result ordering or that the list is static/finite would close the remaining gap.

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?

Schema description coverage is 100%, including a detailed enum explanation for view and an example for search, so the schema does the heavy lifting. The description only restates the filtering option and adds no syntax or semantics beyond it; baseline 3 applies.

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?

A specific verb ("List") plus resource ("currencies SAP Concur accepts") and the fields returned (ISO code and name). The resource noun is distinct enough from siblings like concur_list_payment_types and concur_list_expense_types that an agent can route correctly, though no sibling is named explicitly.

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 phrase "optionally filtered by a code or name fragment" implies the only usage decision this tool requires — whether to pass a search term. There is no explicit when-to-use/when-not guidance or reference to alternatives for looking up currency metadata elsewhere.

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