trty_service

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

Annotations already declare readOnly/idempotent hints, and the description aligns with them. It additionally discloses the oc env-var fallback, the type response formats (JSON/XML/HTML), and the return of 'error', adding behavioral context beyond the structured 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?

The description is compact and well-organized: a title line, a summary sentence, labeled Args/Returns sections, and a concrete example. No unnecessary prose; every sentence contributes to understanding.

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 simple retrieval-by-id tool, the description covers purpose, all parameters, and the return type. It lacks an explicit pointer to trty_search for obtaining the id, but the schema and annotations provide enough for a minimally viable tool. The omission is minor.

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?

With 0% schema description coverage, the description compensates well by explaining id as 'Treaty sequence number', oc as 'Optional OC override (defaults to env var)', and type with enumerated examples. The abbreviation 'OC' is left undefined, but overall the parameter explanations add meaning beyond raw schema fields.

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 opens with 'Retrieve treaty full text' and rephrases as 'This tool retrieves the complete text of a Korean international treaty.' This is a specific verb+resource that clearly distinguishes the tool from sibling search tools like trty_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?

Usage is implied rather than explicit: the tool is for retrieving full treaty text, and the example shows how to invoke it. However, it does not mention that one should first use trty_search to obtain an id, nor does it contrast with other service tools. This is implied guidance, not explicit.

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