cashapp_get_card_info

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

No annotations exist, and the description lists returned fields but omits behavioral details like authentication requirements, idempotency, or data freshness. For a no-parameter read, it is adequate but not thorough.

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?

Single sentence, front-loaded with verb and resource, no redundant words. Efficient and scannable.

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 0-parameter read tool with no output schema, the description sufficiently covers its purpose and returned data. No gaps given the tool's complexity.

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 zero parameters (100% coverage), so no parameter description is needed. Baseline score of 4 applies as description adds no unnecessary detail.

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 ('Get information') and identifies the resource ('linked Cash Card') and data points ('last four digits, status, and type'), clearly distinguishing from sibling tools like cashapp_get_balance.

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 implies usage when card info is needed, but lacks explicit when-to-use, when-not-to-use, or alternative guidance. Sibling tools have distinct purposes, making differentiation implicitly clear.

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