list_cards

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

With no annotations, the description carries the full burden, and it discloses nothing: no read-only confirmation, pagination, rate limits, or caching behavior. The 'fresh' parameter implies a cache interaction with siblings like cache_status and sync_now that is never explained.

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?

A single front-loaded sentence with no waste, but its brevity comes from under-specification rather than efficiency. There is nothing to trim, yet it earns little.

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?

A two-parameter list tool with no annotations and no output schema, and the description supplies none of the missing context: filtering behavior of provider_id, meaning of fresh, or what a card record contains. Inadequate for correct 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?

Schema description coverage is 0%, and the description mentions neither 'fresh' nor 'provider_id'. The non-obvious 'fresh' boolean—presumably whether to bypass a cache—is left completely undefined, so an agent cannot know how to set it.

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 a specific verb (List) and resource (credit and debit cards), which is enough to separate it from list_banks and list_accounts. It stops short of any scope or sibling differentiation (e.g., versus get_card_balance), so it is clear but thin.

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?

No guidance on when to call this versus get_card_balance, list_accounts, or sync_now. The agent is left to infer usage entirely from the name.

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