get_school_info

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

No annotations are present, so the description must carry the full burden of behavioral disclosure. The description only states what the tool does, not any behavioral traits such as data freshness, authentication requirements, error handling, or any side effects. This is insufficient for an agent to understand the tool's behavior.

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 very concise, consisting of a single line and an Args section. While it is front-loaded with the main purpose, it lacks additional context that could be provided without adding much length. It is not overly verbose but misses opportunities to add value.

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 tool has one parameter and an output schema (though not shown), the description is still incomplete. It does not explain what the output contains, how to interpret the results, or any edge cases. For a simple tool, a slightly richer description would be expected.

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?

The schema has 0% description coverage, meaning the parameter complex_no only has a title and type. The description adds '단지 코드' (complex code), which provides minimal semantic value. It does not explain the format (e.g., numeric, alphanumeric), how to obtain it, or any constraints.

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 clearly states that the tool retrieves school districts around a complex (elementary, middle, high school). It uses specific nouns and verbs, making the purpose understandable. However, it does not distinguish itself from siblings like get_complex_detail or get_region_info, which could also provide location-related data.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, context, or scenarios where this tool is appropriate. For example, it does not explain if it should be used after obtaining a complex_no from another tool.

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