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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that — it does not clarify what 'detailed information' includes (e.g., that the review_limit parameter implies reviews are embedded), nor describe any response shape or pagination behavior.

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, front-loaded sentence with no redundant filler. It is efficient, though efficient here partly reflects under-specification rather than disciplined editing.

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?

There is no output schema, so the description carries the burden of explaining what 'detailed information' returns, yet it stays vague and never mentions the embedded reviews implied by review_limit. For a fetch-by-ID tool, this leaves the agent unable to predict the response contents.

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 both parameters (parking_id and review_limit) are already documented in the schema. The description adds no meaning beyond the schema — notably it never mentions that review_limit controls how many reviews come back, which would have tied the parameter to the tool's purpose.

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?

The description states a specific verb ('Get') and resource ('detailed information about a specific parking space'), which distinguishes it from list_* and search_* siblings. However, it does not explicitly differentiate from the closest sibling, get_parking_reviews, which also returns details about a parking space.

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?

There is no guidance on when to use this versus get_parking_reviews, search_parkings, or list_available_parkings. It also omits the obvious prerequisite that an agent must first obtain a parking_id (e.g., via search_parkings) before it can call this.

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