get_demographics

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, covering the safety profile. The description adds output scope but does not disclose additional behavioral traits such as data source (ACS) or response format. It neither contradicts nor enriches beyond annotations, so a 3 is appropriate.

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 a single, tightly packed sentence that starts with the primary action and then enumerates both the response contents and accepted area types. No words are wasted, and the structure is easily scannable.

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?

With no output schema, the description partially covers return value by listing categories, but it does not describe the response structure or edge cases (e.g., invalid area codes). Given the moderate complexity and abundant annotation coverage, it is nearly complete but could clarify what 'profile' means in terms of a single object or data layout.

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 description coverage is 100%, so each parameter is already explained. The description's list of area types mirrors the enum and adds little new meaning. It does provide context on what the output includes, but that does not enhance parameter understanding. Per rubric, baseline 3 is correct.

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 retrieves a 'full demographic profile' for a single geographic area, listing specific data categories (population, income, housing, education, employment, households) and valid area types. This distinguishes it from siblings like get_demographics_category or get_demographics_trend, which target narrower or comparative views.

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 implicitly communicates when to use this tool (when a complete profile for one area is needed) and contrasts with sibling tools by emphasizing 'full profile' and 'single geographic area'. It does not explicitly mention alternative tools or exclusions, but the context is clear enough for an agent to select it appropriately.

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