get-payment-api-spec

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

No annotations provided; description carries the burden. It discloses security-sensitive rules (e.g., skey, HMAC) but does not mention read-only nature, error handling, or response format. Adequate but not comprehensive.

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?

Well-organized into three sections (purpose, API list, security rules). A bit verbose but not excessive. Each section serves a clear purpose.

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 single-parameter tool with no output schema, the description is thorough: explains what it returns, lists valid inputs, and provides essential security context. No gaps.

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 one parameter. The description adds significant value by listing all valid api_name values explicitly, beyond the schema's examples, thus compensating fully.

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 it retrieves the full specification of the MOBILPAY REST API, including parameters and example code. Explicitly distinguishes from keyword search or fuzzy lookup by specifying '키워드 검색이 아닌 특정 API를 정확히 조회할 때 사용합니다.'

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?

Provides usage context (exact API lookup) and security rules (skey, HMAC, approval API). However, it does not explicitly compare with sibling tools like get-nezo-api-spec or get-docs, leaving some ambiguity.

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