kirikiri_tjs2100_import

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 only states the action and format, but does not disclose side effects, whether it writes data, prerequisites, error behavior, or return values. The term 'import' is ambiguous regarding what actually happens to the data.

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 two sentences: one for the core purpose and one for clarification. It is front-loaded and contains no unnecessary words.

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 one-parameter tool, the description covers the essential purpose and includes a helpful sibling distinction. However, it lacks behavioral details (what 'import' does), output expectations, and prerequisites. With no annotations or output schema, these omissions leave gaps for an agent.

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's single parameter 'path' has no description (0% coverage), so the description must compensate. The phrase 'from compiled TJS2100' suggests the path points to a compiled TJS2100 file, but it doesn't clarify expected file extensions or format specifics. This is minimal but usable context.

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 'Import UTF-16 string table from compiled TJS2100 (KrKrZ)', specifying the verb, resource, and format. It also explicitly distinguishes itself from VNTextPatch's scn→json conversion by naming the alternative tool.

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?

It provides an explicit exclusion ('NOT VNTextPatch「scn→json」') and names the correct alternative ('use vntextpatch_extractlocal'). This is useful guidance, though it doesn't discuss other related TJS2100 siblings (export, list_sectors, split/merge), so it's not a comprehensive usage guide.

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