explore_households_get_all

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

With no annotations, description fully owns behavioral disclosure. It only states 'Get All' and the endpoint, omitting crucial details like read-only nature, pagination, sorting, or any side effects.

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?

Extremely concise but at the cost of clarity. Single sentence 'Get All' fails to convey substantive meaning, making it under-specification rather than effective conciseness.

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 8 parameters, no output schema, no param docs, and no annotations, the description is completely inadequate. It does not address pagination, filtering, sorting, or return format.

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?

All 8 parameters lack descriptions in both schema and tool description. The description provides zero information about parameters like 'page', 'orderBy', 'queryFilter', etc.

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?

Description is extremely minimal, only 'Get All' with an HTTP path. It vaguely suggests retrieving all households but does not clarify the resource or distinguish it from similar sibling tools like 'get_all_households'.

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 guidance on when to use this tool versus alternatives. No context about when to prefer this over similar tools or any usage conditions.

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