List Households Statistics

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

No annotations are supplied, so the description carries the full disclosure burden, but it only says 'Get Statistics.' It does not state whether the operation is read-only, what statistics are returned, how scoping works, or what happens when no households exist. Nothing is disclosed beyond the implied GET/list semantics.

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 words with no sentence structure and no meaningful information. This is under-specification rather than effective conciseness, as the words carry almost no usable guidance for an agent.

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?

Although an output schema exists and there are no required parameters, the tool cannot be confidently selected or understood because what constitutes 'households statistics' is undefined. The name and title hint at the resource, but the description supplies no context about response scope or how this differs from related statistics tools.

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 single optional accept-language parameter has 0% schema description coverage, and the description does not mention it or add any semantic meaning. Because schema coverage is low, the description was expected to compensate but instead provides nothing.

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 says only 'Get Statistics,' a generic synonym for the title's 'List Households Statistics' that omits the 'households' scope and any detail about which statistics are included. It does not differentiate this from sibling tools like list_admin_about_statistics or other list endpoints. This is essentially a restatement of the name/title with no added specificity.

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 when-to-use guidance is provided. The description never states when this endpoint should be chosen over list_admin_about_statistics or other household-scoped list tools, and it gives no context such as admin vs. household-scoped statistics.

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