get_census_place_metrics

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the default behavior (latest year, server-chosen) and clarifies that data is public-domain. It does not mention potential side effects, but as a read-only getter this is acceptable.

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: function, behavior, and parameter explanation. It is front-loaded with the primary purpose and avoids any filler.

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 the tool's single parameter and the existence of an output schema, the description is complete. It covers the tool's role, the default year behavior, and parameter specifics without redundant return-value details.

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 only defines 'fips' as a string with no description (0% coverage). The description fully compensates by explaining what fips is and the length variations by geographic level. This is essential for correct use.

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 opens with a specific verb and resource: 'Get the full set of US Census metrics for one place, grouped by category.' This clearly states what the tool does. It distinguishes itself from siblings by positioning it as a 'Census profile' for a single place.

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 advises using this when you want a broad Census profile: 'Use this as a "Census profile" for a single place.' This implies when to choose it over metric-specific tools, though it does not explicitly name alternatives or exclusions.

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