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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety behavior is covered. The description adds the HTTP endpoint and enumerates returned fields, which is useful because there is no output schema, but it does not describe error behavior, permissions, or rate limits.

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 two compact fragments with no wasted wording: the entity, id-based scope, returned fields, and endpoint are all front-loaded. Nothing extraneous is present.

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 read-only single-record GET with fully documented parameters, the description is largely complete and lists the returned fields in lieu of an output schema. Minor gaps remain around not-found behavior and explicit sibling routing, but nothing essential to invoking the tool is missing.

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%, with both event_id and event_part_id fully documented in the schema, including the ext: prefix convention and the source of event_part_id. The description adds only 'by id' and does not extend parameter meaning beyond the schema, so baseline 3 is appropriate.

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 identifies a specific resource and scope: one event part (session) retrieved by id, with the exact endpoint and returned fields. It is clearly distinguishable from the sibling list tool evenium_list_event_parts because it fetches a single part by id.

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 phrase 'by id' implies a single-record lookup, and the schema notes that event_part_id comes from evenium_list_event_parts. However, the description itself does not explicitly state when to use this tool instead of the list tool or what failure cases mean, so usage guidance is only implied.

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