explain_egovframe_component

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

With no annotations, the description disclosure that the tool is read-only ('읽기 전용') and lists all return elements. This gives clear behavioral context. It does not mention potential failure modes or permissions, but for a simple read tool this is adequate.

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 a single sentence that efficiently packs all key details. While it uses parentheses for a list, it remains clear and front-loaded. No unnecessary words, though the list could be formatted more cleanly.

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?

The tool has low complexity (one parameter, no output schema). The description explains what the return value contains, which is sufficient for the agent to understand the output. It could mention that the component must exist, but the example mitigates this.

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 100% coverage with a description for the id parameter. The description adds an example ('예: bbs'), which is helpful but does not provide additional meaning beyond what the schema already states. Baseline score is appropriate.

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 returns detailed information about a single common component, listing specifics like description, dependencies, tables, guide links, and installation commands. It uses a specific verb and resource, and the name 'explain' distinguishes it from siblings that list, search, or add components.

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 implies usage when you need full details of one component, but it does not explicitly state when to use this tool versus alternatives like list_egovframe_components or get_egovframe_guide. No exclusions or prerequisites are mentioned.

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