weekend_events

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

With no annotations, the description must carry behavioral disclosure alone. It only says 'Find events' and does not mention result limits (size parameter), ordering, pagination, or any side effects. The existence of the size parameter and its impact on results is entirely undisclosed.

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 one short sentence that is front-loaded with the main action and contains zero unnecessary words. It is appropriately sized for the tool's simplicity.

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 two-parameter tool with no output schema, the description covers the core action but leaves notable gaps: it does not state the return format, the effect of the size parameter, or how results are ordered. It is minimally viable but lacks detail needed for full comprehension.

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 describes city but not size, and the tool description adds no semantics for either parameter. The size parameter, with its default of 8 and maximum of 20, is completely unexplained, and the description only reinforces the city parameter's basic meaning already present in the schema.

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 states the tool's purpose with a specific verb ('Find'), resource ('events'), and scope ('this weekend' in a given city). It distinguishes from siblings by the weekend-specific focus, which is not present in search_events or events_by_category.

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 use for weekend-specific event lookups, but does not explicitly contrast with alternatives like search_events or events_by_category. There is no 'when not to use' guidance, leaving the timing of choosing this tool over siblings implicit.

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