get_events

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

With no annotations, description covers behavior: auto-pagination, returned fields (title, times, location, notes, label color). Includes label color mapping. Does not mention side effects or rate limits, but is fairly transparent.

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 well-structured sentences. Front-loaded with core purpose and auto-pagination. Label color details are relevant and appended without redundancy.

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 no output schema, description lists key return fields. Lacks details on pagination mechanics and full return structure, but adequate for a simple fetch operation.

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 coverage is 100% (baseline 3). Description adds value for 'start_after' by advising on date-to-timestamp conversion. Other parameters are sufficiently described.

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?

Description clearly states 'Get all events from a specific TimeTree calendar', specifying the resource (events) and action (get). It distinguishes from siblings like 'get_updated_events' by mentioning automatic pagination to fetch all events.

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 (e.g., 'get_updated_events' for partial updates). Usage context is implied but not directly compared.

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