crm_get_events

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

No annotations are provided, so the description carries the full burden. It indicates the tool is read-only through 'Get' and 'viewing', and mentions filtering and pagination behavior. However, it does not disclose potential limitations, default sorting, or whether all events are returned. It is adequate but not rich.

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 with a related-tools line. It is front-loaded with the key purpose and adds relevant sibling references without fluff.

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?

No output schema is present, but the tool is a simple read operation. The description covers the use case and filtering/pagination, and the schema documents all six parameters. Related tool references add context. It is reasonably complete for a straightforward list tool.

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%, with each parameter (page, sort_by, end_date, per_page, sort_order, start_date) already described. The tool description only says 'filtering and pagination' without naming parameters or adding format details, so it does not go beyond the schema. Baseline 3 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?

The description clearly states the tool retrieves calendar events ('Get calendar events from CRM'), specifies the use case ('viewing meetings, appointments, and scheduled activities'), and distinguishes from sibling tools by naming alternatives (crm_create_event, crm_create_task, crm_get_notes).

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 explicitly states when to use this tool ('Use for viewing meetings, appointments, and scheduled activities') and provides alternative tools for related purposes (crm_create_event for scheduling, crm_create_task for follow-ups, crm_get_notes for meeting notes), giving clear when/when-not guidance.

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