kya_getCard

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

Discloses card is single-use, self-destructs after use, user's real card never enters chat, and MFA approval needed. No annotations exist, so the description adequately covers behavioral traits.

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?

Five sentences each adding value, front-loaded with main purpose, uses imperative language, no fluff. Efficient and well-structured.

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?

Describes process and lifecycle but lacks explanation of output (return value). No output schema is provided, so this gap is notable. However, the moderate complexity and clear process partially compensate.

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% with decent descriptions for each parameter. The description does not add significant extra meaning beyond the schema, so 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?

Clearly states the tool gets a single-use virtual Visa for purchases, with specific verb 'Get' and resource 'card'. Differentiates from sibling tools by referencing prerequisites (kya_getAgentIdentity) and follow-ups (kya_reportPurchase).

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?

Explicitly requires calling kya_getAgentIdentity first and kya_reportPurchase after, establishing a clear usage sequence. Does not explicitly state when not to use or alternatives, but the context implies it's for purchases only.

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