Ontology MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the tool returns a file path ('생성된 이미지 파일 경로를 반환하며') and that this path must be communicated to the user ('이 경로는 반드시 사용자에게 알려주어야 합니다'). However, it doesn't disclose important behavioral aspects like whether this is a read-only or mutating operation, potential rate limits, authentication requirements, error conditions, or what happens when files are saved. The description adds some value but leaves significant gaps.

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 reasonably concise with two sentences. The first sentence states the core functionality, and the second provides important behavioral information about the return value. There's no obvious fluff or redundancy. However, it could be slightly more front-loaded by immediately clarifying the tool's scope relative to siblings.

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 complexity (11 parameters, no annotations, no output schema), the description is moderately complete. It covers the basic purpose and return behavior but lacks important context. Without annotations or output schema, the description should ideally explain more about what kind of operation this is (read vs write), error handling, and the format/meaning of the returned file path. The current description provides a foundation but leaves the agent with significant uncertainty about the tool's full behavior.

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 description coverage is 100%, meaning all parameters are documented in the schema itself. The description doesn't add any parameter-specific information beyond what's already in the schema descriptions. It mentions model selection automation but doesn't explain parameter implications or interactions. With complete schema coverage, the baseline score of 3 is appropriate as the description doesn't enhance parameter understanding beyond the structured data.

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 the tool's purpose: 'Google Gemini 또는 Imagen 모델을 사용하여 이미지를 생성합니다' (uses Google Gemini or Imagen models to generate images). It specifies the verb ('생성합니다' - generates) and resource ('이미지' - images). However, it doesn't explicitly differentiate from sibling tools like 'mcp_gemini_create_image' or 'mcp_imagen_generate', which appear to have similar functionality.

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 provides some implied usage context: '모델 이름에 따라 적절한 API가 자동으로 선택됩니다' (the appropriate API is automatically selected based on the model name). This suggests the tool handles model selection automatically. However, it doesn't explicitly state when to use this tool versus alternatives like 'mcp_gemini_create_image' or 'mcp_imagen_generate', nor does it provide any exclusion criteria or prerequisites.

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