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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile needs no restatement. The description earns credit for disclosing the shape of the read: it returns evidence behind each attribute, approved community check-ins, and credited creator posts, which tells the agent what depth of data to expect. It does not mention behavior on an unknown slug or any rate limits.

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 the usage trigger first and the payload enumeration second; nothing is redundant. The payload list is dense with parentheticals but each item is informative rather than filler.

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 and only one parameter, the description carries the return-value burden well by enumerating what comes back. It is essentially complete for a read-by-id tool; only error behavior for an invalid or unknown slug is unaddressed.

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?

The single `slug` parameter is fully documented in the schema with an example, and the description only restates that lookup is by slug. With 100% schema coverage and one required param, the description adds no syntax, format, or validation meaning beyond the schema, so the 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 everything about ONE spot by slug") and enumerates the payload categories: address, opening hours, Wi-Fi/outlets/noise/calls with evidence, best time, access tips, check-ins, creator posts, links. The capitalized "ONE" distinguishes it from the list-oriented siblings search_spots and recommend_spot.

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 says to use it "after search_spots/recommend_spot (or when the user names a specific place)," which tells the agent both the sequencing and the direct-lookup trigger. It stops short of an explicit when-not or an alternative for bulk detail retrieval, but the context is clear.

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