get_case_detail

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

No annotations are provided, so the description carries full burden. It adds behavioral context about the result containing a url link, but does not explicitly state that the tool is read-only or disclose any authorization requirements or side effects.

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?

The description is two sentences with no extraneous words. The first sentence states the main functionality, and the second adds a useful detail about the URL. Information is front-loaded.

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?

Given the complexity of returning full case detail and the absence of an output schema, the description adequately lists the components (overview, persons, etc.) and mentions the URL. It does not describe output structure, but the listed components provide sufficient context.

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 (id) described as '사건의 UUID'. The description repeats that the tool returns case content but adds no additional semantics about the parameter, such as format or constraints, staying at the baseline for high coverage.

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?

The description uses a specific verb '반환합니다' (returns) and identifies the resource as '사건 한 건의 전체 내용' (entire content of one case), listing specific components. This clearly distinguishes it from sibling tools like list_cases (which lists cases) and update_case_info (which updates).

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 provides no guidance on when to use this tool versus alternatives. It does not specify that this is for retrieving full detail vs. summary, nor does it mention alternatives like list_cases for overviews.

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