get_attendee_report

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

No annotations are present, so the description carries the full burden: it discloses the HTTP method and endpoint (GET /reports/attendees/), a specific list of 400 errors, and the required authentication header, which are rich behavioral details not available elsewhere.

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 labeled sections (endpoint, errors, auth) and front-loads the core purpose. It is efficient, though the 'Same parameters as sales report' line could be replaced with direct parameter guidance to reduce cross-referencing.

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?

There is no output schema, so the description should ideally explain return values, which it does not. However, it provides endpoint, error codes, and auth requirements that are essential for correct invocation, making it reasonably complete for a report-retrieval 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 100%, so the schema already documents all five parameters (event_ids required, plus end_date, timezone, start_date, event_status). The description adds no parameter-specific meaning beyond pointing to another tool for shared parameters, so 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?

The description states a specific verb (Retrieve) and resource (Attendee Report) plus the primary lookup key (Event ID or status). It distinguishes itself from sibling get_sales_report by name and by explicitly referencing it, though the audience/subject is not clarified beyond the title.

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 usage via 'by Event ID or status' and points to get_sales_report for shared parameters, but does not state when to use this tool over get_sales_report or list_attendees, nor any prerequisites beyond the auth token requirement.

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