list_simdasi_districts

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

With no annotations, the description carries the full burden. It adds useful context beyond the schema: the SIMDASI domain, the 7-digit format, and the need for a parent regency code. However, it does not disclose output structure, error behavior, or potential edge cases such as empty results or invalid parent codes, leaving notable gaps for a tool with no output schema.

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 two short sentences, front-loaded with the primary action and resource, then a direct, useful instruction for obtaining the required parent code. Every sentence earns its place with no redundancy.

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 single-parameter list tool, the description covers what it lists, the domain, and the prerequisite parent code. The lack of an output schema means the exact return format is not explicitly stated, but 'List 7-digit MFD codes' strongly implies an array of code strings, making it largely complete for its low complexity.

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 already provides 100% coverage for the single 'parent' parameter with a clear description. The tool description adds value by explaining how to obtain the correct parent MFD code via list_simdasi_regencies, which is practical guidance beyond the schema's static field description.

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 uses the specific verb 'List' and identifies the resource as '7-digit MFD codes for districts in a regency', with context that it is used in SIMDASI. It clearly distinguishes from sibling tools by scoping to districts and referencing list_simdasi_regencies for the parent code, making the hierarchy explicit.

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 explicitly instructs to use list_simdasi_regencies to get the parent MFD code, which is a clear prerequisite and points to an alternative tool for the parent level. It does not explicitly state when not to use this tool (e.g., for provinces or regencies), but the parent-child framing implies the appropriate usage context.

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