get_service_details

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral context on top: no API key required, an error is returned for nonexistent/removed listings, and a paused listing is still viewable but not orderable. That paused-vs-orderable distinction is a non-obvious state rule an agent could not infer from annotations.

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?

Front-loaded with purpose and the returned field list, then prerequisites, then error/state behavior. It is fairly dense in a single paragraph, but nearly every clause (error case, paused state, custom-price caveat) carries distinct operational value.

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 no output schema, the description compensates by enumerating the returned fields, and it covers the failure mode, the paused-listing edge case, and prerequisites. Nothing an agent needs to call this correctly 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 the single service_id parameter is fully documented in the schema, including its origin. The description restates it as a 'numeric ID' but adds no format, bounds, or edge-case 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 ('Get the full public details of one service listing by its numeric ID') and enumerates exactly what is returned (title, category, price, provider, rating, description, delivery time, listing link). It is clearly distinguishable from siblings like search_services or get_pricing_info.

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?

Names both sources of IDs ('from search_services or get_recommended') and the precise moment to call it ('just before hire_worker'). It even routes custom-priced listings to a separate agreement step with the provider first, giving explicit when-to-use sequencing.

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