Fetches full text, photos, and extracted facts for a single rental ad, including heating and parking details, so you can verify a listing before recommending it.
Full description, photos and extracted facts for one ad. Use it before recommending a listing: heating and parking are often only in the full text.
| Name | Required | Description | Default |
|---|---|---|---|
| url | Yes | URL of an ad on storia.ro, publi24.ro or lajumate.ro (e.g. from search_rentals). |
Changes observed during successful MCP inspections.
v0.1.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare read-only, idempotent, open-world behavior, so the description does not need to restate safety. It adds useful context about what is returned and why full-text detail matters, though it omits format and error behavior details.
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 short sentences, front-loaded with the return contents and followed by the decision-relevant usage rule. No wasted wording.
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 one-parameter read-only detail tool with full schema coverage and clear annotations, the description supplies enough about return contents and when to call it. No output schema exists, but the description still names the key returned information.
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 coverage is 100%, and the schema already explains that the URL must be from storia.ro, publi24.ro, or lajumate.ro and can come from search_rentals. The description adds no URL-specific semantics beyond what the schema provides, so the 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?
States the specific resource and contents: full description, photos, and extracted facts for one ad. Clearly distinguishes a single-listing detail lookup from bulk search siblings, though it does not explicitly name those siblings.
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?
Gives a clear usage trigger: 'Use it before recommending a listing,' and explains why by noting heating and parking are often only in the full text. No explicit exclusions or sibling names, but the context is strong.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.