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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds useful behavioral details: it returns the same fields as search_listings and the escortfox.com link, while contact details and photos are only available on that page.

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 compact and front-loaded with the core operation. Every clause adds practical value: the id format, the relationship to search_listings fields, and where contact details and photos live.

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 read tool with no output schema, the description sufficiently explains return content, the id source, and what is not returned. Schema and annotations then cover language selection, safety, and idempotency.

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%, so both parameters are already documented. The description still adds meaning for the required id parameter by explaining that it is the numeric value at the end of a listing link (…/anna-12345 → 12345), which helps agents extract the correct value.

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: get the summary of one EscortFox listing by numeric id. It also distinguishes this single-listing lookup from search_listings by explaining that it returns the same fields as that sibling and adds the listing's escortfox.com link.

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?

Clearly implies when to use it: when you have a listing's numeric id, derived from the end of a listing URL. It does not explicitly say to use search_listings when you do not already have an id, but the context is otherwise clear and the id-source example is helpful.

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