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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful scope ('ONE' listing, includes the Teppek contact route) but says nothing about behavior on an unknown/stale id, id reuse across sources, or rate limits — minor but real gaps for a lookup tool.

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 tight sentence with the resource and scope front-loaded, followed by the routing condition. No filler, no repetition of the title or annotations.

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?

With an output schema present, return values need no explanation, and the annotations plus a 100%-covered single parameter leave little else to disclose. The only gap is what happens on a missing or invalid listing_id, which the description omits.

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 fully documented in-schema, including its provenance ('id field of search_listings, semantic_search or list_my_listings') and a concrete example. The description only restates 'by id' and adds no syntax or format detail beyond the schema, so 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 specific verb and resource ('Fetch the full detail of ONE Teppek listing by id') and enumerates the returned fields (title, description, price/salary, location, contact route). The 'ONE' emphasis and the 'after search_listings' framing clearly separate it from the bulk siblings search_listings, semantic_search and list_my_listings.

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?

Explicitly routes the agent: 'Use after search_listings to show, summarize or compare a specific job, home, vehicle or service the user picked.' It names the prerequisite sibling and the intent (show/summarize/compare one item), though it does not state an explicit exclusion such as 'do not use to browse multiple listings — use search_listings instead'.

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