kirikiri_tjs2100_list_sectors

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

With no annotations, the description must carry the behavioral disclosure burden. It only says 'List', which implies a read-only operation, but does not disclose what the output looks like, whether the path should be a file or directory, any restrictions, or side effects. This is a significant gap for a tool with zero annotation coverage.

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 with no fluff, but it is under-specified rather than appropriately concise. It lacks essential context about the path parameter and the nature of the listing, making it only minimally useful.

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 tool's low complexity (1 parameter, no output schema), the description still fails to provide complete context. It does not explain what 'sectors' are, what 'KrKrZ Split metadata' means, or what information the listing returns. The absence of an output schema makes this omission more critical.

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 a single `path` parameter with no description, and schema coverage is 0%. The description does not compensate: it never explains what `path` should refer to (e.g., a file, directory, or archive path). Parameter semantics are completely undocumented.

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 states a specific verb and resource: 'List TJS2100 DATA/Other/TJS2 sectors' and adds '(KrKrZ Split metadata)' for context. This clearly distinguishes it from sibling TJS2100 tools like kirikiri_tjs2100_import, export, split, and merge.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention any preconditions, use cases, or exclusions, leaving the agent without any direction for selection.

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