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 'read-only' (a safety trait) and the date format, but does not mention any other behavior such as whether party_size affects availability, data freshness, or error conditions. The disclosure is minimal and largely redundant with the 'get' in the tool name.

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 a single, focused sentence with no redundant words. It is appropriately concise and front-loads the key information ('Read-only availability').

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?

The tool has three parameters including an optional party_size, but the description only hints at the date. With no annotations and minimal description, the agent lacks information about how to correctly invoke the tool (e.g., what product_id refers to, how party_size alters behavior). Although an output schema exists, it does not cover parameter semantics or usage context. The description is too sparse for a 3-parameter tool.

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 0%, so the description must explain parameters. It only adds meaning for 'date' (format). 'product_id' is not explicitly mapped to the activity, and 'party_size' is entirely unexplained. The description fails to compensate for the lack of schema descriptions.

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 clearly identifies the tool as providing availability for an activity on a specific date, with a format hint. It distinguishes itself from sibling tools (details, search, recommendations) by focusing on availability. However, it lacks an explicit verb like 'get' or 'check', relying on the tool name for the action.

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?

No guidance is given on when to use this tool versus alternatives like get_activity_details or search_activities. The description only states what the tool does, not when it should be chosen over siblings.

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