get_my_upcoming_events_for_home_page

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds valuable context about the curated future-only nature of the result and the shape as an `upcomingEvents` array, which is beyond structured fields. No contradiction with annotations.

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 compact and well-structured: the first sentence states the purpose and return type, and the second sentence gives clear alternatives. Every word earns its place, with no redundancy.

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 description fully covers the tool's purpose, scope, and relationship to sibling tools. With rich annotations, an output schema, and a single optional parameter, no additional context is needed for safe and effective use.

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 single optional `fields` parameter is fully described in the input schema with an extensive list of dot-path options, so schema coverage is 100%. The description does not add further parameter details, but the schema is rich enough that the baseline of 3 is appropriate.

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 retrieves upcoming Partiful events specifically for the home page 'Upcoming' view and returns an `upcomingEvents` array. It uses a specific verb and resource, and distinguishes itself from sibling tools like get_my_rsvps and get_published_events.

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 gives explicit guidance on when to use this tool versus alternatives: it is the future-only, home-page-curated subset, while get_my_rsvps covers complete RSVP/invite history and get_published_events covers hosted-only events regardless of date. This clearly delineates usage contexts.

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