list_census_topics

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

There are no annotations provided, so the description carries the full burden. It states the operation is a list, implying non-destructive behavior, but it does not disclose any specific behavioral details such as auth requirements, pagination, or data format. The description is minimal but not misleading.

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. The main purpose is front-loaded in the first sentence, and the second provides essential prerequisite guidance. No wasted 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?

This is a simple tool with one parameter and no output schema. The description explains what it lists and where to get the required ID. It doesn't describe the return format, but that might be inferred from 'data topics'. Given the simplicity, the description is adequate but could benefit from a note about the response structure or field names.

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 has 100% coverage for the sole parameter 'kegiatan' with its description 'Census activity ID (from list_census_events)'. The tool description reinforces this by saying 'Use list_census_events to get the activity ID', but it doesn't provide additional syntax or format details beyond the schema, so a baseline of 3 is appropriate.

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 a specific verb 'List' with a clear resource 'data topics' and scope 'for a specific census activity', distinguishing it from sibling tools like list_census_areas and list_census_datasets by the resource type.

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 says 'Use list_census_events to get the activity ID,' providing a clear prerequisite and directing the agent to a sibling tool for the required parameter. However, it doesn't explicitly state when not to use this tool vs other census listing tools.

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