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

No annotations are provided, so the description bears full responsibility. It states 'Heuristic itinerary' implying an approximate algorithm but does not disclose limitations, such as whether results are recommendations or bookings, or if it covers all available events. Critical behavioral traits like non-determinism or lack of reservation capability are omitted.

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 sentence, making it concise. However, it uses jargon ('Heuristic itinerary') that may confuse agents and lacks front-loading of the primary action. Still, it is not verbose.

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 4 parameters and no output schema or annotations, the description is incomplete. It does not specify the return format (list of venue IDs? object with time slots?), whether the tool books anything, or how conflicts are resolved. A planner tool needs more context on its operational scope and output.

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?

Parameter description coverage is 100% via schema, so the baseline is 3. The description does not add extra semantic meaning beyond the schema, e.g., it mentions 'morning/afternoon/evening picks' but doesn't map these to parameters like 'window' or 'interests'. It adds no new value over the 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 'Heuristic itinerary: morning/afternoon/evening picks matching interests within a window' clearly indicates the tool generates an itinerary divided into time slots based on interests. It distinguishes itself from siblings like get_event or search_events by focusing on creating a multi-part plan rather than retrieving individual events. However, it could be more explicit with a verb like 'Creates'.

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 provides no guidance on when to use this tool versus alternatives like search_events or whats_on. Sibling tools are listed but no exclusions or context for selection are given.

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