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

With no annotations provided, the description carries the full burden. It discloses that the operation is read-only, lists key response fields, and importantly flags that certain listing fields contain authoritative eligibility/logistics rules that should be checked before answering guest questions. This is useful behavioral context beyond the basic operation.

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?

The description is two sentences, front-loaded with the core purpose, and every clause adds value. It is concise without being under-specified.

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 simple one-parameter detail lookup with an output schema available, the description is complete. It explains the operation, names response fields, and highlights the authoritative data fields, which is more than sufficient for an agent to invoke and interpret results.

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 schema has a single required parameter `product_id` with zero description coverage in the schema. The tool description only loosely implies that the parameter identifies the activity/product, but does not explain its format, source, or how to obtain a valid value. Given the low coverage, the description should have compensated more explicitly.

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 uses a specific verb and resource: 'Read-only details for a single activity/product.' It clearly distinguishes itself from sibling tools like search_activities (searching) and get_activity_availability (availability), making the purpose immediately apparent.

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?

The description implies when to use the tool—when needing details for a single activity/product—and contrasts with the broader search tool. However, it does not explicitly exclude when to use siblings like get_activity_availability or get_complementary_recommendation, so it stops short of full guidance.

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