get_houses

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

With no annotations, the description minimally implies a read-only operation via 'list'. However, it does not disclose auth needs, rate limits, or scope (e.g., if 'your houses' means owned or visible). Adequate but not rich.

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 – one sentence, seven words. Front-loaded with the verb and resource. No wasted words.

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 zero-parameter tool with no output schema, the description is adequate but lacks detail on return format, pagination, or user scope. Could be more complete but meets minimum needs.

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?

No parameters – baseline 4 per guidelines. The description adds no parameter info, but none is needed since schema coverage is complete (100% of 0 params).

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 'List your houses and who lives in them' clearly states the verb (list) and the resource (houses, inhabitants). It distinguishes from sibling tools like get_my_baselings or get_assignments, which cover different data.

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. There is no mention of context, exclusions, or when not to use it among a list of 50+ sibling tools.

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