kirikiri_kagex_locate_template

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

With no annotations provided, the description carries the full burden. It adds behavioral context by stating 'no binaries' and indicating the search location and environment variable fallback in the parameter description. However, it does not disclose what the tool returns (e.g., a path) or behavior when the template is not found.

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 exceptionally concise: two short clauses front-loaded with the verb 'Locate'. Every word contributes meaning, including the path and the 'no binaries' clarification. No wasted text.

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 simple locate tool with one optional parameter and no output schema, the description covers the essential aspects: what it locates, where, and what it excludes. It could be more complete by explicitly stating the return value (e.g., the resolved path), but overall it provides enough context for an agent to use it correctly.

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 input schema fully documents the only parameter (template_dir) with a description, achieving 100% schema coverage. The description adds no additional parameter semantics beyond what the schema already provides, so the baseline score of 3 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 the tool's action: 'Locate KAGeXpress Template', with a specific path (源码/kagexpress/Template) and an explicit scope exclusion ('no binaries'). This distinguishes it from sibling tools like kirikiri_kagex_init_project or apply_config, which perform different actions on templates.

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 explicit guidance on when to use this tool versus alternatives. The name and description imply it is for locating the template directory, but there is no mention of prerequisites, related workflows, or when to prefer this over other tools that might also reference templates.

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