Get one ImotAI listing

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

With no annotations, the description carries the burden and does well: it discloses the negative scope (no broker free-text, contact details, or exact coordinates) and characterizes marketContext as authoritative per-listing. It does not cover auth requirements or error/not-found behavior, keeping 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?

A single front-loaded sentence that leads with the action and key, then enumerates return content. Dense but every clause adds information; the long field list makes it slightly heavier than ideal.

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?

No output schema exists, so the description correctly enumerates what is returned and what is excluded. Combined with a single required parameter, an agent has enough to call it correctly; only permission/error context is missing.

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 only one parameter exists, so the schema already documents the UUID-or-slug semantics. The description merely restates 'by its id or slug' without adding format constraints, so the baseline 3 applies.

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?

States a precise verb (Get) and resource (one ImotAI listing) plus the lookup key (id or slug), and enumerates the returned data fields. An agent can distinguish this from list_search-oriented siblings without opening the schema.

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 implied: 'one listing by its id or slug' contrasts with search_properties and get_market_stats, but there is no explicit when-to-use statement or advice such as 'use search_properties first to obtain an id'.

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