포트원 V2 프론트엔드 코드 예제 읽기

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

Description contradicts the input schema: it claims all args except framework are optional, but schema marks pg and pay_method as required. No other behavioral traits disclosed, and no annotations provided.

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?

Description is relatively concise with three sentences, but the third sentence contains inaccurate information, reducing effectiveness.

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?

No output schema or annotations. Description fails to explain return format, language, or example structure. Incomplete for a code example tool.

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%, but description adds contradictory guidance on required fields. It does not meaningfully augment parameter understanding.

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 that it fetches Portone V2 frontend code examples, distinguishing it from sibling tool readPortoneV2BackendCode. Title reinforces the purpose.

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 instructs to call this tool first before writing any code related to Portone V2, providing clear context. However, it does not specify when not to use or mention alternatives explicitly.

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