list_flats_by_occupancy

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the core listing/filter behavior and does not mention pagination behavior, authentication requirements, rate limits, or any other operational details. This is minimal transparency for a tool with no annotations.

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 a single, concise sentence that is front-loaded with the verb and resource. It contains no filler or redundant information, earning full marks for conciseness and structure.

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?

The tool is a simple list operation with a single required filter and two pagination parameters. The schema fully documents the parameters, and the description explains the core purpose. It does not overcomplicate, and while it doesn't mention pagination behavior, that is adequately covered by the schema. Given the simplicity and schema coverage, the description is sufficiently complete.

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%, so the parameters are fully documented in the schema. The description only reiterates the flat_occupancy_id filter that already appears in the schema, adding no extra semantic value beyond what the schema provides. Baseline 3 applies.

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 uses a specific verb ('List') and resource ('flats') with a clear filter scope ('filtered by a specific flat_occupancy_id'). It clearly distinguishes from the sibling tool 'list_flats' by indicating the occupancy-based filter.

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?

The description implies the tool is for listing flats for a given flat_occupancy_id, which suggests a use case, but it does not explicitly state when to prefer this over alternatives like 'list_flats' or provide exclusions. The filter mention gives some context, but there is no direct alternative guidance.

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