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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description does add value by naming the returned data (blob names, sizes, quota, status) in the absence of an output schema, but says nothing about pagination, ordering, or empty-house behavior.

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?

It is a single terse fragment with no waste, but it is under-specified rather than genuinely concise — there is no front-loaded statement of the action, only a noun phrase.

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 must convey what the tool returns, and it only gestures at that cryptically. It also never explains that 'house' means encrypted file storage, which is critical given four sibling house_* tools and a house_plans tool that could easily be confused with it.

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 api_key parameter, which already documents the Bearer/env alternatives, so the baseline of 3 applies. The description contributes nothing beyond the schema here.

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 fragment implies a list operation over 'your private house' and enumerates what it surfaces (blob names, sizes, quota, status), but the verb is never stated and 'house' is never identified as encrypted file storage, so the title has to carry the resource definition. It does not distinguish itself from the close siblings house_get, house_put, or house_delete.

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?

There is no statement of when to call this versus alternatives such as house_get (single item) or house_plans, nor any prerequisite or context. An agent must infer usage entirely from the 'list' framing.

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