Sessionize

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

With no annotations provided, the description carries the full burden. It discloses the return format (speaker details) and the default event behavior, but lacks information on potential limitations like rate limits, error handling, or pagination. It does not contradict any 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 front-loaded with the core purpose, followed by output details and parameter guidance in two efficient sentences. Every sentence adds necessary information without waste.

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's low complexity (one optional parameter, no annotations, no output schema), the description is mostly complete for a read-only list operation. It covers purpose, output, and parameter logic, but could improve by addressing behavioral aspects like error cases or data freshness.

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%, so the schema already fully documents the single optional parameter. The description adds minimal value by reiterating the default event behavior, but does not provide additional syntax or format details beyond what the schema states.

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 the specific action ('List all speakers'), resource ('for a Sessionize event'), and output details ('speaker names, bios, taglines, and social links'), distinguishing it from siblings like 'findSpeaker' (likely for individual lookups) and 'getSessionsBySpeaker' (session-focused).

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?

It provides clear context on when to use this tool (to retrieve all speakers for an event) and includes a conditional rule for the eventId parameter (uses default if not provided). However, it does not explicitly state when not to use it or name alternatives among siblings like 'findSpeaker' for specific speaker searches.

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