List Currencies

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

Annotations already indicate readOnly, idempotent, non-destructive. Description adds that it returns specific currency fields and how they relate to other entities. No mention of pagination or rate limits, but these are standard for list tools.

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 concise sentences. First sentence states the action and what is returned; second sentence connects the output to other tool usage. No wasted words, front-loaded with key information.

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, good annotations, and full schema coverage, the description is complete. It explains both what the tool does and how to use its output in downstream operations (deals, orders, products).

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 has 100% description coverage with top and skip parameters. Description does not elaborate beyond schema but uses default values (top=50, skip=0) implicitly. The baseline is met, but no added value for parameters.

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?

Description explicitly states it lists available currencies in Ploomes CRM, gives examples (BRL, USD, EUR), and mentions return fields (Id, Symbol, Name, etc.). This clearly differentiates from sibling list tools like ploomes_contacts_list or ploomes_products_list.

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?

Directly states 'Use the returned Id as CurrencyId when creating deals, orders, or products', providing clear context for when the output is needed. Lacks explicit 'when not to use', but the purpose is unambiguous and no alternative tool exists for currencies.

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