events_detail

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

With no annotations, the description carries full burden. It tells the action is read-only implicitly but does not disclose any behavioral traits like side effects, authentication requirements, or rate limits. 'Full details' is vague without referencing the output schema.

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?

Concise, well-structured with Args section and inline formatting. Every sentence adds value. No fluff.

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 an output schema exists, the description doesn't need to detail return values. It mentions partial match which is important context. However, it does not explain what 'full details' encompasses or how it relates to sibling tools, but overall adequate for a detail look-up 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?

Schema has 0% description coverage, but the description adds significant meaning: 'Full or partial event name to look up (case-insensitive)' for event_name, and 'Calendar year — "2025" or "2026" (default: "2026")' for year, including allowed values and default.

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?

Clear verb+resource: 'Get full details for a specific event by name.' Distinguishes from siblings like events_search (list) and events_upcoming (upcoming events) by specifying 'full details' for a single event.

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 explicit guidance on when to use this tool versus alternatives like events_search or events_upcoming. It states 'by name' but does not specify prerequisites or when to choose this over list-type tools.

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