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

Annotations already establish this as read-only, idempotent, and non-destructive. The description adds useful behavioral context beyond annotations by specifying what the response contains (description, all photos, features, agency contact), which is especially valuable given no output schema is present.

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 two short sentences, bilingual, and front-loaded with the core action and object. No filler or redundant elaboration exists; the bilingual repetition is reasonable given the Bulgarian title and context.

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-by-id tool with one parameter, the description is complete: it explains what resource is fetched, how it is identified, and what major data categories are returned. It could add explicit guidance about invalid or missing ids, but overall it gives the agent what it needs to invoke the tool 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%, and the single parameter is well documented as 'Listing id from search_properties'. The tool description simply repeats 'by id' without adding semantic detail beyond the schema, so baseline 3 is appropriate.

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 specific verb ('Get'), a specific resource ('one real estate listing'), and the key identifier ('by id'). It also names the included payload categories (description, photos, features, agency contact), which clearly distinguishes it from listing-oriented siblings like search_properties and list_locations.

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 makes the usage context clear: call this when full details of a single listing are needed. The schema parameter description, 'Listing id from search_properties', further implies it should be used after search_properties, though the description itself does not explicitly state when not to use it.

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