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

Annotations already declare readOnly, idempotent, and closed-world, so the safety profile is covered. The description adds genuinely useful context beyond that: the service is free, the intermediary is licensed and Czech-specific, and the return payload is phone/e-mail/links. It does not cover edge cases (e.g., what happens if no advisor is available), which keeps it short of a 5.

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?

Two tight sentences with no filler, and the return payload is stated up front in the second sentence. The first sentence is slightly roundabout in its 'How the user can...' construction but remains economical.

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, no-output-schema tool, the description supplies the missing return-value information (phone, e-mail, links) that an agent would otherwise have to guess. It is sufficient to invoke correctly, with the only gap being the absence of explicit routing guidance against siblings.

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 the baseline is 4. The description appropriately does not invent parameter details and instead spends its words on what the call yields.

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 states a concrete outcome (obtaining a binding assessment and free mortgage arrangement via a licensed Czech intermediary) and specifies what is returned (phone, e-mail, links). It is clearly distinct from the sibling rate/calculation tools, though the 'How the user can get...' framing makes the tool's own action slightly indirect rather than an explicit verb+resource.

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?

Usage is only implied: an agent can infer this is for users wanting personalized mortgage advice rather than raw rates or calculations. There is no explicit when-to-use statement, no statement of when not to use it, and no mention of the sibling tools it should be chosen over.

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