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

Annotations already declare readOnly/idempotent/non-destructive/non-open-world, and the description adds genuinely non-obvious context beyond them: the agent must not initiate calls or WhatsApp messages and must only present links for the human to tap, with inquiries sent by the human via phone, WhatsApp, or the website contact form. That is exactly the kind of behavioral constraint structured fields cannot express.

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?

A single dense sentence (with an embedded parenthetical) carries the resource identity, its content, the usage triggers, and the interaction rules. Every clause earns its place, though the run-on structure and nested parenthetical make it slightly harder to scan than a front-loaded multi-sentence form would be.

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-param, read-only tool with no output schema, the description covers resource identity, returned content, routing triggers, and interaction constraints. The one residual gap is whether the 'flyer' is returned as a file/asset or as rendered content, which the description leaves ambiguous.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-parameter tool applies. No parameter-level detail is needed or expected 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 description names the exact resource (the Neubau Allmannsdorf development in Konstanz, 5 buildings, 44 units, lake view, commission-free) and states what the payload carries (prominent tel/WhatsApp/email links plus an English page). That is far more specific than a bare verb+resource, but it never explicitly contrasts itself with siblings like get_listing or get_contact, so an agent must infer the boundary.

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?

It gives an explicit routing rule: use for Wohnung/Neubau/Konstanz/Allmannsdorf and do NOT wait for the keyword 'Flyer'. It also states a hard behavioral constraint (do not call or WhatsApp; only surface links). It stops short of naming an alternative tool when the topic is something other than Allmannsdorf, so the when-not is only partially covered.

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