Mieter

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds no operational context beyond that: it does not say whether the default call spans all properties or one, whether the result set is large/paginated, or how the 'last settled' date relates to billing periods.

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 short sentence with no filler, but it is not front-loaded with the tool's action, and it spends its only sentence on return-field content that the output schema presumably already covers.

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?

An output schema exists, so explaining returned fields is unnecessary, and that is essentially all the description does. It leaves the default scope (all properties?) and the effect of the filters unaddressed, which are the details an agent actually needs to call this correctly.

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%, including clear German descriptions for property_id ('nur Mieter dieser Immobilie') and current_only ('nur Mieter, die heute dort wohnen'). The description adds nothing about these filters, so the baseline 3 applies since the schema carries all parameter meaning.

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 reads as a noun phrase listing returned fields (tenant, apartment, move-in/out, last-settled date) rather than stating an action such as 'list tenants'. Combined with the name list_tenants the intent is inferable, but the description itself never says it retrieves a collection, and it does nothing to distinguish it from siblings like list_apartments or list_properties.

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 guidance on when to call this tool, no mention of the two available filters, and no reference to any alternative for related tenant information. The agent must infer entirely from the name that this is the way to enumerate tenants.

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