list_currencies

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

With no annotations, the description carries the burden of disclosing behavior. 'List' unambiguously indicates a read-only operation with no side effects. The description also clarifies the scope ('all currencies supported'), which adds useful context. It doesn't mention authentication or response structure, but these are not critical for a simple list tool.

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 a single, concise sentence that front-loads the action and object. Every word earns its place ('List', 'all', 'currencies', 'supported by PocketSmith').

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 zero-parameter list operation, this description is complete. The absence of an output schema is mitigated by the clear 'List all currencies' phrasing, making the return value (a list of currency identifiers or objects) predictable. No additional behavioral or contextual information is necessary for this simple tool.

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 accepts zero parameters, and the input schema is an empty object. The description correctly implies no arguments are needed. Since there are no parameters to describe, the baseline score of 4 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?

The description uses a specific verb 'List' and clearly states the resource 'all currencies supported by PocketSmith'. It distinguishes from the sibling tool get_currency, which retrieves a single currency, by explicitly indicating the full set. No ambiguity.

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 clearly indicates this returns the complete set of currencies, implying it should be used when a full enumeration is needed. However, it does not explicitly mention the alternative get_currency for single-currency lookups, so it lacks explicit when-to-use-vs-alternatives guidance.

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