get_demographics

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

The description transparently lists the demographic categories returned, giving a clear picture of the output. It notes the data is from the 2021 Census and keyed to the output area. However, it does not mention potential limitations like data staleness or rate limits.

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 sentences: first states the action and target, second lists contents. Every sentence adds value 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?

Given an output schema exists (implied), the description provides sufficient context on what data is returned. It explains the data is aggregated to the output area, which is useful. Could mention that the data is specific to 2021 UK Census, but overall complete for a specialized lookup tool.

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 describes the single parameter (postcode) with format details. The description adds no additional parameter context beyond what is in the schema, so it meets the baseline for full schema coverage.

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 tool returns an ONS Census 2021 demographic profile for a postcode, listing specific categories (population, age bands, etc.). This distinguishes it from sibling tools like get_crime or get_broadband, which return different data types.

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?

No explicit when-to-use or when-not-to-use guidance is provided. The purpose is implied, but there are no comparisons or exclusions regarding alternatives like get_postcode_profile.

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