list_events

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

No annotations provided. Description states non-destructive listing and includes mention of returned details (workout descriptions/steps), but lacks info on pagination, rate limits, or potential large responses. Minimal behavioral disclosure.

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 concise sentences with no redundant words. Purpose, resource, scope, and return value efficiently communicated.

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?

For a simple list tool with two parameters and no output schema, description covers purpose, input constraints, and return value. Lacks ordering or default behavior but sufficient.

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% with descriptions for both 'oldest' and 'newest'. Description does not add meaning beyond stating date range; baseline score applies.

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 'List', specific resource 'calendar events', examples of types, and date range scope. Distinguishes from siblings like list_activities and list_workouts.

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?

Implied usage for reading calendar events within a date range, but no explicit when-to-use or when-not-to-use guidance, nor comparisons with sibling tools like create_event or update_event.

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