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

Annotations cover the safety profile (readOnly/idempotent/non-destructive), but the description adds auth posture ('unauthenticated, and repeatable'), the error contract for unknown ('404') and missing venue_id, and the scope of what is NOT returned (occupants, visits, other agents' data). That is substantial context beyond the structured fields.

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?

Purpose and ordering are front-loaded and the price-vs-charge distinction is genuinely useful. However, it is dense and long, and it enumerates the full return field list even though an output schema exists, which is redundant padding rather than 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?

For a single-parameter read tool with annotations and an output schema, the description covers usage sequencing, scoping, auth, error cases, and result semantics. Nothing an agent needs to call it 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 coverage is 100% and the venue_id description already names its source, but the description adds value by clarifying acceptable provenance (a list_venues id, not a real-place id) and the error behavior of a missing id. It stops short of adding id-type or format detail, so it sits above the baseline-3 but not at 5.

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 ('Read one DrinkedIn fictional venue') and immediately scopes it against siblings, naming list_venues, enter_venue, find_places and plan_evening. An agent can distinguish this read tool from the write/enter tools without opening any schema.

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?

Explicit sequencing ('after drinkedin_list_venues and before drinkedin_enter_venue'), an explicit source for the id ('a venue_id from that list'), and explicit exclusions ('not a real place from drinkedin_find_places or drinkedin_plan_evening'). It also contrasts itself with drinkedin_order_drink as the tool that actually orders.

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