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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds a paging model and the shape of returned content, but it does not say what happens when both name and slug are supplied, or when neither is (all parameters are optional), which matters 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?

Two sentences, no filler, with the core purpose front-loaded and the paging hint placed after it. Every clause carries information an agent can act on.

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, listing the returned fields is exactly the right compensation, and the schema is fully documented. The remaining gap is the lack of any note that at least one of name or slug is effectively needed even though the schema marks nothing required, plus the absence of a pointer to list-parking for slug discovery.

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%, so the baseline is 3; the description adds only the note that offset/maxChars exist to page through long descriptions and that either slug or name may identify the lot. Those are useful framing points but add little beyond the parameter descriptions themselves.

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?

A concrete verb-plus-resource statement ("Get full details for one parking lot by slug or name") that also enumerates the returned fields (fee, hours, surface, coordinates, canonical URL). It is clearly distinct from the list-parking sibling, though the description never names that sibling or explains that it is the way to discover slugs.

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?

It gives useful in-tool guidance for paging ("Use offset and maxChars to page through long descriptions"), which tells the agent how to handle oversized content. It stops short of true selection guidance: no mention of when to prefer get-spot or list-parking, and no statement of the prerequisite that a valid slug/name must exist first.

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