search_nodes

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states it searches entities without explaining what the search returns, whether it's paginated, what search algorithm is used, whether it requires authentication, or any rate limits. This leaves critical behavioral aspects completely unspecified for a search operation.

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 extremely concise (just three Korean words), but this brevity comes at the cost of being under-specified rather than efficiently informative. While front-loaded in the sense that there's only one statement, it fails to provide the necessary information that would justify its place in a tool definition.

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 search tool with no annotations, no output schema, and 0% parameter documentation, the description is completely inadequate. It doesn't explain what entities are being searched, what the search returns, how results are structured, or any constraints. Given the complexity of search operations and the complete lack of structured documentation, this description fails to provide the necessary context.

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 for the single 'query' parameter, the description provides no additional semantic information about what the query parameter should contain, its format, syntax, or examples. The description doesn't mention the parameter at all, leaving the agent with no guidance on how to construct effective search queries.

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 '엔티티를 검색합니다' (searches entities) is a tautology that essentially restates the tool name 'search_nodes' without providing meaningful differentiation. While it identifies the action (search) and target (entities), it doesn't specify what kind of entities, what search criteria beyond the query parameter, or how this differs from sibling tools like 'list_entities' or 'get_entity_names'.

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 no guidance on when to use this tool versus alternatives. With sibling tools like 'list_entities', 'get_entity_names', and 'open_nodes' that might serve similar purposes, there's no indication of when this search tool is appropriate versus those listing tools, nor any prerequisites or constraints for its use.

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