get_landlord_profile

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It explicitly warns not to invent missing legal name, street, or IBAN, which is valuable behavioral guidance against hallucination. However, it does not disclose whether the operation is read-only, what the response structure is, or how empty fields are represented beyond the warning.

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 very short and free of fluff; two sentences deliver a resource and a key caution. It is efficient but somewhat fragmentary ('Stored Vermieter letterhead') which slightly reduces clarity. Overall, it earns high marks for not wasting 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 simple get tool with one parameter and no output schema, the description should at least mention what the output represents and how the parameter works. It partially covers the data (letterhead) and includes a warning about empty fields, but omits any description of return format, successful/failed responses, or the role of teamId, leaving it incomplete.

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 0% and the description does not mention the 'teamId' parameter at all. The parameter name is self-explanatory, but the description fails to connect it to 'a space' or explain how it is used. With no parameter info in the schema, the description should compensate but does not.

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 (Vermieter letterhead for a space) but lacks a clear active verb like 'get' or 'retrieve', making it a noun phrase rather than an explicit action. It does not distinguish itself from sibling tools, many of which are similarly listed as get/list operations.

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 use this tool instead of alternatives. It does not mention prerequisites, when not to use it, or how it relates to sibling tools like get_unit or list_units. The single sentence provides no contextual usage direction.

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