eb_my_orders

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

The readOnlyHint annotation already declares the safety profile. The description adds that the event is expanded in the response and that time_filter filters orders by event time. It does not mention pagination or return structure, but given the annotation, it provides sufficient added context beyond the schema.

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, front-loaded sentence with no filler. It states the verb, resource, scope, and a key parameter behavior efficiently.

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 list tool with two optional parameters, no output schema, and a read-only annotation, the description covers the essential purpose and scope. It could mention pagination explicitly, but the schema's continuation parameter covers that, and the 'event expanded' note gives context on the response.

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% for both parameters. The description adds a brief explanation of time_filter's purpose ('narrows to upcoming or past events') but doesn't expand on continuation. With full schema coverage, the baseline is 3, and the added description is marginal.

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 uses the specific verb 'List', identifies the resource as 'ticket orders', qualifies the scope as the authenticated user's, and adds 'attendee side' to distinguish from organizer tools like eb_org_orders. It also notes the event expansion, making the purpose unambiguous.

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 clearly implies usage for viewing the current user's own orders on the attendee side, which differentiates from sibling tools for organizers (eb_org_orders) and event-specific orders (eb_event_orders). However, it does not explicitly name alternatives or state when not to use this tool.

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