get_event

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

The description gives no behavioral disclosure beyond the verb 'get'. With no annotations, it does not state that the operation is read-only, safe, or any other traits, leaving the agent to assume the obvious but without explicit confirmation.

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 that conveys the purpose without any filler or redundancy. Every word earns its place.

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 simple read operation with one well-documented parameter, the description is adequate. It does not describe return structure, but the phrasing 'details' implies that. Without output schema or annotations, a bit more context could be useful, but it is largely complete for this trivial tool.

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 input schema already fully documents event_uuid with the description 'UUID of the event to retrieve'. The tool description adds no additional meaning beyond 'specific event', which is already implied by the schema and tool name.

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 'Get details of a specific event' clearly names the verb (get) and resource (event), and the qualifier 'specific' distinguishes it from the sibling list_events. It is unambiguous about what the tool does.

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 like list_events or cancel_event. The description does not mention any context or exclusions for usage.

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