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

With no annotations, the description carries the full behavioral burden and does so: API key required, rate limit (3/day free, then 1 credit each), one item per call, no bulk export, and a provenance guarantee that every citation passed law.go.kr verification. These are exactly the operational constraints an agent cannot infer from schema or annotations.

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?

Front-loads the two things an agent must know first (key + cost), then usage, then guarantees. The bilingual Korean/English pairing doubles the length with translated repetition, which is somewhat redundant but each section still earns its place.

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 exists, and the description compensates by enumerating the returned fields per question type, including citation provenance. For a four-parameter retrieval tool with cost implications, nothing material is left unexplained.

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%, so the baseline is 3, but the description adds genuine meaning by mapping parameter combinations to output shapes (no → MCQ payload; format → essay/record payload) beyond the schema's field-level docs. Enum values are also reinforced contextually.

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?

States a specific verb and resource ('Fetch ONE bar-exam question with its full gold answer') and enumerates exactly what comes back for each format (prompt, 5 choices, ministry answer, commentary, notes, cited statutes/precedents). The scope statement 'one item per call — not available for bulk export' cleanly separates it from bulk/search siblings like bar_exam_search.

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?

Gives explicit invocation recipes per format: '선택형: round+subject+no' and '사례형·기록형: round+subject+format', so the agent knows which parameters to combine for each question type. It lacks an explicit 'use bar_exam_search to discover question numbers first' pointer, so it is clear on context but silent on the sibling alternative.

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