get_event_details

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

The description adds the behavioral detail of formatting the output as a clickable markdown link, which goes beyond the readOnlyHint annotation. No contradiction with annotations.

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 concise, front-loaded with purpose, includes necessary usage instruction, and has no redundant sentences. Every sentence provides value.

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 presence of an output schema, the description is complete. It covers the key information needed: purpose, parameter, and presentation format. No gaps remain.

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 has 0% description coverage, but the description provides a brief definition for 'event_number' with an example. This compensates for the missing schema description sufficiently.

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 'Get full details for a specific Tekna event', which is a specific verb+resource. It distinguishes from siblings like search_events (search vs specific) and get_news, get_member_benefits (different resources).

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 provides clear instructions on how to present results (always include event link as clickable markdown). However, it does not explicitly state when to use this tool versus alternatives, though the specificity of the event number implies it's for single-event retrieval.

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