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

With no annotations, the description carries the full behavioral burden. It usefully discloses the return contents (blob names, sizes, quota, status) and implies scoping via 'your private house', but never states that it is a read-only query, whether results are paginated, or how quota/status are surfaced.

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?

A single terse fragment with no wasted words and the resource front-loaded. It is efficient, though arguably underspecified rather than optimally structured.

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?

For a simple one-parameter list tool with no output schema, naming the returned fields is adequate to convey the result shape. Still missing is any usage context distinguishing it from sibling house tools, which caps completeness at 'minimum viable'.

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% for the single optional api_key parameter, so the schema already documents the auth mechanism. The description adds nothing about parameters, which matches the baseline of 3 when the schema does the heavy lifting.

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 identifies the resource ('your private house') and the returned fields (blob names, sizes, quota, status), which implies a listing operation. However, there is no explicit verb, and it never distinguishes itself from close siblings like house_get, house_put, or house_delete, leaving the agent to infer that this is the list variant.

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 given, and no alternatives are named. In a cluster of house_* siblings (get/put/delete/plans) the description does not tell the agent when to pick this tool over house_get or house_plans.

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