get_census_data

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 discloses the prerequisite behavior (must call list tools first) and clarifies that data is actual census data, not metadata. However, it does not discuss return format, error handling, or size, limiting transparency.

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 sentences, front-loaded with the tool's core function followed by a practical prerequisite note. Every word earns its place.

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 data-fetch tool with no output schema, the description provides the essential purpose and required ID sourcing, which is largely sufficient. However, lack of output schema means little is said about the return shape, though the tool name and description imply raw census data.

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% with each parameter description referencing the source list tool. The description adds sequential ordering ('use ... first') that synthesizes the three parameters into a workflow, going beyond individual schema descriptions.

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 'Fetch' with the resource 'actual census data' and specifies three dimensions (activity, area, dataset). This clearly distinguishes it from the sibling list_census_* tools, which provide IDs rather than data.

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, list_census_areas, and list_census_datasets first to obtain required IDs, providing clear step-by-step context. It does not explicitly mention exclusions or alternatives, but the prerequisite guidance is strong.

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