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

Without annotations, the description carries the full burden. It discloses key behaviors: silently drops non-attendee IDs, returns in order requested, max 20 IDs, and access requirements ('open to any active DCer who can see the event'). Lacks details on rate limits or error handling, but overall transparent.

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 well-structured with clear sections (URL, return, use case, query, behavior, access). Every sentence adds value, no fluff. Front-loaded with essential purpose and method.

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?

Given the tool has 2 params and no output schema, the description covers purpose, usage, behavior, and access. It lacks explicit return format details, but these may be inferred from context or sibling tools. Overall sufficiently complete for an AI agent to select and invoke correctly.

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 coverage is 100% and already provides detailed descriptions (e.g., 'Comma-separated userIDs (max 20). Non-attendees are silently dropped.'). The description adds context about URL structure and use-case, but minimal additional parameter semantics. Baseline 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?

Description clearly states it returns agendas (bookmarked sessions + meetup RSVPs) for multiple attendees in a single call, using a specific verb ('Get') and resource ('multiple attendees' agendas'). It distinguishes from sibling tools like 'event_agenda' which likely covers single attendees.

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?

Explicitly states when to use: 'when an AI agent needs to plan around several DCers at once — comparing schedules, finding shared sessions, building a meetup invite list.' Implicitly differentiates from single-attendee alternative. Does not explicitly state when not to use, but the context is clear.

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