pretalx_list_schedule_sessions

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

With no annotations, the description carries the full burden of behavioral disclosure. It mentions case-insensitive filtering and a flattening operation, but does not explain what 'flatten' means, whether the tool is read-only, what the return structure is, or any side effects. This is insufficient for a tool with zero annotation support.

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 short sentence and is front-loaded, but it is under-specified. 'Flatten' and 'filters' are vague, and no detail is provided, making the brevity a drawback rather than an asset.

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 no annotations, 0% schema coverage, and six parameters, the description leaves critical behavior unexplained. It does not clarify how filters combine, what include_raw does, or what flattening produces. The presence of an output schema does not compensate for the missing parameter and behavior semantics.

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%, and the description only says 'optional case-insensitive filters' without mapping to any of the six parameters. It does not explain the meaning of day, room, event, track, speaker, or include_raw, nor how filters interact.

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 'Flatten schedule sessions' as a verb-resource pair, but 'flatten' is ambiguous and does not clearly state that this tool lists sessions from a schedule. It also does not distinguish itself from siblings like pretalx_get_schedule or pretalx_find_schedule_conflicts.

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 usage guidance is provided. The description does not say when to use this tool versus alternatives such as pretalx_get_schedule or other listing tools. The phrase 'optional case-insensitive filters' implies usage but gives no context or exclusions.

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