pretalx_list_submissions

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'List submissions... with optional server-side filters', which largely restates the schema. No details on pagination, event identifier format, filtering behavior, rate limits, or required permissions are provided.

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 sentence, front-loaded with the action and resource. It is appropriately concise with zero wasted words, though the brevity comes at the cost of substantive explanation.

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 no annotations and no schema descriptions, and despite the presence of an output schema, the description is too sparse. It does not explain how to specify an event, valid values for limit/state/track, what include_raw does, or how this listing relates to search_submissions, leaving significant gaps for an agent.

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 0%, so the description must compensate. The phrase 'optional server-side filters' is generic and does not explain any of the six parameters (event, limit, state, track, include_raw, submission_type) or their intended formats, restrictions, or interactions.

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 a specific verb 'List' and resource 'submissions', scoped to 'an event', making the primary action clear. It hints at server-side filters but does not explicitly differentiate from sibling tools like pretalx_search_submissions, which could be a near-identical use case.

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?

No guidance is provided on when to use this tool versus alternatives such as pretalx_search_submissions or pretalx_get_submission. There is no mention of prerequisites, exclusions, or scenarios where a different tool would be more appropriate.

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