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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the result is an estimate carrying a source and page URL, which is useful behavioral context, but says nothing about precision, rounding, or how the two scale parameters interact.

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?

It is short and front-loads the conversion scope, which is good, but a repetition of the title plus an external URL and a trailing return-value sentence dilute it. No sentence is harmful, but the title restatement earns little.

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 3-parameter tool with 0% schema description coverage and no output schema, the description leaves the parameter semantics and return format largely unexplained. The one caveat about formula variation is the only substantive content beyond the title.

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 should carry the burden, yet it says nothing about score, to_scale, from_scale, their defaults, or the conversion direction. The enum values (4.5/4.3/4.0) are self-documenting in the schema, but the description contributes no parameter meaning.

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 restates the title verbatim ('학점 비례 환산 (GPA scale conversion 4.5 / 4.3 / 4.0)') rather than describing the operation, but the title/name together do convey a GPA scale conversion across 4.5/4.3/4.0. It never states the direction of conversion or distinguishes itself from siblings like naesin_grade or suneung_score.

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?

It offers a caveat ('단순 비례 환산(참고용)' and that schools/companies use different formulas so the target's criteria take priority), which hints this is an approximation tool, but gives no explicit when-to-use condition and names no alternative tool.

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