event_my_registration_answersList the signed-in user's own answers to one event's registration
questions. Only ever returns their own data — use
event_registration_responses (organiser only) to read other people's.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Page number, starting at 1. | |
| page_size | No | Rows per page (max 100). | |
| event_slug | Yes | Slug of the event. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already covers the safety profile. The description adds useful scoping context by stating 'Only ever returns their own data,' but it does not describe return format or pagination behavior, so the added behavioral transparency is moderate.
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?
Two tightly written sentences with no filler. The core behavior is front-loaded, and the alternative tool is mentioned only where it adds real value.
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 read-only list tool, the description is complete enough: it states the resource, the ownership scope, and the alternative for other users' data. The schema covers all parameters, and the annotations cover side-effect safety.
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 input schema fully documents event_slug, page, and page_size. The description does not add parameter-level detail beyond the schema, so the baseline of 3 applies.
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 opens with a specific verb and resource: 'List the signed-in user's own answers to one event's registration questions.' It also distinguishes itself from the alternative event_registration_responses by emphasizing that this tool only returns the caller's own data.
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 explicitly tells the agent when to use this tool versus the alternative: use this for the signed-in user's own answers, and use event_registration_responses (organiser only) to read other people's. This is direct, unambiguous routing guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are grouped by domain prefix and mostly target a distinct resource, but there are several near-overlapping read clusters — notably whoami/event_roles/event_my_membership (all answer 'what roles at event X'), submission_get/submission_page, team_open_roles/team_seeking_members, and company_employees/company_roster. The descriptions do an exceptional job of steering ('use this, not that'), so misselection is unlikely, but the sheer number of such pairs keeps this from a 5.
The dominant domain_prefix + noun/verb pattern (event_, team_, submission_, company_, article_) is consistent and readable. Deviations: list_api_endpoints/list_capabilities invert the word order (verb-first) versus event_list/submission_list elsewhere, search and whoami carry no domain prefix, account_how_to_sign_in is a phrase, and read verbs vary between get/list/browse/page/preview.
60 tools is far beyond the 25+ threshold, and the surface is purely read-only — the breadth comes from extremely granular views (22 event_* tools) and many singleton catalogs (event_cities, event_types, event_background_images, article_languages, tag_list, tech_list, company_vacancies) plus six meta/informational tools. The domain is genuinely broad and every tool is distinct, so it reads as heavy rather than chaotic, but the count is still excessive.
The set contains zero write tools — no create, update, or delete anywhere — yet the descriptions repeatedly direct callers to absent tools: event_create, event_set_branding, event_add_sponsor, event_submit_registration_answers, invite_join, team_post, team_assign_role, team_remove_member, company_fire_employee, account_export_data, and more. An agent following the descriptions will call nonexistent tools and fail. The read/browse coverage is very thorough, but the complete absence of the write side (which the descriptions themselves treat as existing) is a significant gap.