list_census_areas

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

With no annotations, the description carries the burden of disclosing behavior. It provides a workflow and indicates that the output is used elsewhere, but it does not explicitly state whether the operation is read-only or require any permissions. For a simple list operation, the implication is there, but it could be more explicit.

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 three concise sentences, front-loaded with the purpose. Every sentence adds value: purpose, prerequisite, and output usage. No fluff or 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 tool with one parameter and no output schema, the description provides the essential context: how to get the parameter and what to do with the result (MFD codes). It could be more complete if it described the return format or any pagination, but for this simplicity level it is adequate.

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?

Schema coverage is 100%, so the baseline is 3. The description adds context by tying the parameter to 'a specific census activity' and referencing list_census_events, which mirrors the schema description. It does not provide additional syntax or format details beyond 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 clearly states the action ('List available areas/regions') and the resource ('for a specific census activity'). It references the prerequisite tool (list_census_events) and downstream usage (get_census_data), which distinguishes it from other list_* siblings.

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_census_events to get the activity ID, providing a clear prerequisite. It also mentions that the returned MFD codes are used as wilayah_sensus in get_census_data, establishing workflow context. However, it does not list exclusions or alternative tools.

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