list_simdasi_tables

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

No annotations are provided, so the description carries the full burden. It only discloses the requirement for a wilayah code and its source, but does not describe the return value, pagination, or side effects. For a list operation, output behavior is left unspecified.

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?

Two short, front-loaded sentences with no filler. The main action is stated first, and the constraint follows in the second sentence.

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 one-parameter list tool, the description is adequate. However, the absence of an output schema and any description of the returned data structure leaves a gap for agents needing to know what 'list tables' actually returns. The prerequisite helps but does not fully address output semantics.

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 already describes 'wilayah' as '7-digit MFD code of the area' (100% coverage). The description adds provenance by stating the code comes 'from list_simdasi_provinces', which is meaning not present in the schema.

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 'List' as a specific verb, identifies the resource as 'SIMDASI tables', and scopes it to 'a specific area' via a wilayah code. This clearly differentiates it from siblings like list_simdasi_provinces and get_simdasi_table.

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 states a clear prerequisite: 'Requires a 7-digit MFD wilayah code from list_simdasi_provinces,' which tells the agent how to obtain the input. It does not explicitly mention alternative tools or exclusions, but the context is clear for the intended use case.

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