pretalx_get_submission

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

With no annotations provided, the description carries the full burden for behavioral transparency. 'Fetch full details' indicates a read operation, but it does not disclose whether the response includes all fields (e.g., reviews, raw data) or what 'full' means relative to the include_raw parameter. No mention of permissions, error behavior, or side effects.

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 words. Every word is useful, and it immediately conveys the core purpose without unnecessary 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?

Given the tool has three optional parameters, no annotations, and no parameter descriptions, the description is insufficient. It does not explain how to specify which submission, what the event parameter is for, or how include_raw affects the response. The absence of any usage prerequisite makes the tool hard to invoke correctly in 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?

The schema has zero parameter descriptions and the description adds no meaning to any of the three parameters (event, include_raw, submission_code). There is no hint that submission_code identifies the target or that include_raw modifies the payload, leaving the agent completely unguided on how to fill the parameters.

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 'Fetch' with the resource 'full details for one submission,' clearly distinguishing this from sibling tools that list or search submissions. It's one precise sentence that leaves no ambiguity about the tool's function.

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 implies use when a single submission's full details are needed, but it does not explicitly state when to use this tool instead of pretalx_list_submissions or pretalx_search_submissions. No alternatives or exclusions are mentioned, so the guidance is only implicit.

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