pretalx_list_speakers

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

No annotations are available, and the description only adds 'compact output' — it does not disclose default behavior for omitted event, pagination limits, or the meaning of include_raw. This is insufficient for a tool with no annotation safety/behavior metadata.

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?

Single short sentence, no filler, and the key verb/resource appear immediately. However, brevity sacrifices necessary detail.

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?

With three optional parameters, no annotation coverage, and no explanation of parameter semantics, the description is not adequate for selection/invocation. The presence of an output schema does not compensate for missing behavioral and parameter context.

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 0% and the description mentions no parameters. The phrase 'compact output' only weakly implies the include_raw toggle, and 'event' and 'limit' are left entirely to schema types/defaults.

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 clearly states the action ('List speakers') and the scope ('for an event'), with 'compact output' hinting at a limited response format. It does not explicitly call out sibling tools like pretalx_search_speakers or pretalx_get_speaker, so it lacks explicit differentiation.

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 list endpoint versus searching speakers or retrieving a single speaker. Context signals include many sibling tools but the description gives no exclusions or alternatives.

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