Retrieves card metadata for a network token, enabling verification of tokenized payment details through read-only access.
Retrieves card metadata for a network token. This tool ONLY reads data.
| Name | Required | Description | Default |
|---|---|---|---|
| payment_method_token | Yes | The token of the network-tokenized payment method |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, and the description repeats 'This tool ONLY reads data' without adding new behavioral context (e.g., auth requirements, rate limits, or side effects). No contradiction, but minimal added value.
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 short, front-loaded sentences with no superfluous words. Every part serves a purpose: action, resource, and read-only emphasis.
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?
Adequate for a simple read tool with one parameter and readOnlyHint annotation. However, the absence of an output schema and lack of detail on the returned metadata slightly reduces completeness. Could mention typical metadata fields.
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 coverage is 100% with a clear description for the one parameter. The description does not elaborate on what 'card metadata' includes or provide additional context beyond the schema.
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 clearly states the action ('Retrieves') and resource ('card metadata for a network token'), and explicitly declares it is read-only, distinguishing it from sibling tools that may perform writes or retrieve other entities.
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 indicates when to use the tool (when needing card metadata for a network token) but does not provide guidance on when not to use it or mention alternatives among sibling tools. No usage exclusions or comparisons are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.