timetree_list_events

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

With no annotations, the description itself states the important read-only trait and the overlapping-date-range behavior. It does not disclose return shape, pagination, or any other operational details, but for a read-only list tool the disclosed traits cover the main behavioral risk.

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?

Two brief sentences deliver the essential action, scope, and read-only trait with no filler. The core information is front-loaded.

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 five parameters, low schema coverage, and no output schema, the description is too sparse. It does not clarify what calendar_id does, how query filters work, what the response contains, or what happens when no parameters are supplied—information an agent would need to invoke this tool correctly.

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 only 40%, and the description adds no parameter-specific meaning. Only start_date and end_date are described in the schema; query, limit, and calendar_id are left undocumented in both schema and description, so the description does not compensate for the coverage gap.

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 ('Read'), the resource ('TimeTree events'), and the core scope ('overlapping a date range'). It also says 'This tool is read-only', which separates it from event mutation tools like create/update/delete.

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 implies the tool should be used when events need to be read within a date range, and 'read-only' hints it is not for writes. However, it gives no explicit guidance on when to choose this tool over other read-oriented siblings like list_event_comments or list_memos.

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