detc_service

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

Annotations already indicate readOnly and idempotent behavior. The description adds meaningful context beyond that, such as how the 'sections' parameter alters the payload ('summary' excludes 전문), the effect of 'type' on response format, and the 20KB constraint for PlayMCP.

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 well-organized with Args, Returns, and Examples. It is reasonably concise, though the examples and some parameter details could be trimmed without losing essential meaning.

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?

There is no output schema, so the description compensates by stating that the tool returns full decision text or an error. It also gives concrete examples and behavior around response size. It could still mention prerequisites or limitations, but it is complete enough for a read-only retrieval 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 0%, so the description carries the burden. It explains id as a Constitutional Court sequence number, lm as an optional decision name, sections as summary/full mode, and type as JSON/XML/HTML. Only 'oc' remains vague as 'Optional OC override'.

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 states a specific action and resource: 'Retrieve Constitutional Court decision full text' (헌재결정례 본문 조회). This clearly distinguishes detc_service from sibling search tools such as detc_search, and the service pattern is apparent.

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?

Usage guidance is implied rather than explicit. It recommends sections='summary' for PlayMCP to stay under 20KB, but it does not explicitly say when to choose this tool over detc_search or other sibling retrieval tools.

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