listEvents

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

With no annotations provided, the description carries full responsibility for disclosing behavioral traits. It fails to mention that the operation is read-only, whether authentication is required, or how pagination works (despite the schema including pagination parameters). The agent is left unaware of potential side effects or constraints.

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 concise sentence (13 words) that conveys the core action and available filter options. It is front-loaded with the essential purpose and contains no fluff or redundant information.

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 has 7 optional parameters and no output schema, the description is too minimal. It does not explain what the output contains (e.g., list of event objects), how pagination works, or any ordering/limits. The agent lacks sufficient context to use the tool effectively without additional external knowledge.

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 100% parameter description coverage, so the baseline is 3. The description redundantly lists a few filter parameters without adding new meaning (e.g., how filters combine, data types, or format expectations). It does not compensate for the lack of additional semantic context.

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 action ('List'), the resource ('events'), and the source ('from FUB'). It also explicitly lists several filter options (personId, type, property address), making the tool's purpose immediately understandable and distinguishable from singular retrieval (getEvent) or creation (createEvent).

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 no guidance on when to use this tool versus alternative list tools (e.g., listAppointments, listCalls) or how to choose between filters. It does not mention preferred usage patterns, limitations, or exclusions, leaving the agent without decision-making context.

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